3 ms·
You can by deleting the EXTERNALLY-MANAGED file [1] I know some Python maintainers think users are too dumb to work with system Python, but there are also some
by geerlingguy 3y ago
You can by deleting the EXTERNALLY-MANAGED file [1]
I know some Python maintainers think users are too dumb to work with system Python, but there are also some packages that are really hard to deal with on a system level if you try installing them in a venv. Plus venv's are dumb (I use Docker if I need more than one environment for specific apps or dev work), since it's another layer of abstraction I'd need to learn just to use Python.
I'm not forced to use virtual environments for PHP, Ruby, Java, etc... why for Python?
[1] https://www.jeffgeerling.com/blog/2023/how-solve-error-externally-managed-environment-when-installing-pip3 https://www.jeffgeerling.com/blog/2023/how-solve-error-exter...
- nicolaslem 3y agoI think that what bothers you with virtual environments is simply the name. A venv is literally just a directory with files in it. Most of the languages you mentioned actually use a very similar approach to installing dependencies, they just don't call it "virtual", they call it GOPATH, node_modules or something similar. As a developer working mostly with Python I am so glad to have way to install a dependency in a directory that won't break my OS and without having to use docker. I still use docker for lots of things, but not as a way to resolve issues that can be resolved by creating a new directory.
- delfinom 3y ago>I know some Python maintainers think users are too dumb to work with system Python, No, this isn't python maintainers thinking users are too dumb. This is distro maintainers fed up with false bug reports and broken systems caused by python's inability of versioning the packages fed to programs without venv.
- nsteel 3y agoUsing --break-system-packages is a far clearer way to do the same thing.