this post was submitted on 11 Jan 2025
52 points (93.3% liked)

Python

6516 readers
31 users here now

Welcome to the Python community on the programming.dev Lemmy instance!

πŸ“… Events

PastNovember 2023

October 2023

July 2023

August 2023

September 2023

🐍 Python project:
πŸ’“ Python Community:
✨ Python Ecosystem:
🌌 Fediverse
Communities
Projects
Feeds

founded 2 years ago
MODERATORS
[email protected]
[email protected]
[email protected]
52
Yes, you should use a Python venv in a container like docker (www.bitecode.dev)
submitted 6 days ago by [email protected] to c/[email protected]
41 comments fedilink hide all child comments
 

via https://framapiaf.org/@bitecode/113810446556732210

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 3 points 5 days ago (2 children)

You still have the option to choose not to use a venv and risk breaking your user space.

The changes make this harder to do it by accident by encouraging use of a venv. Part of the problem is that pip install --user is not exactly in the user space and may in fact break system packages, and as you wrote, the user shouldn't be able to inadvertently change the OS.

[–] [email protected] 2 points 5 days ago* (last edited 5 days ago)

So the problem here is that you can inject code into a system python process because they run with the user's python install location on their path.

They've fixed the wrong "root cause".

[–] [email protected] 1 points 4 days ago

Makes more sense and I agree, especially with the apparent ease of pip install --user. But there should be no barriers when the root user is used with pip install --system.