Everything is working fine for me.
The externally-managed-environment has very little with the python team and more so to do with the OS distro maintainers. If you wish it to stay the way it used to be, nothing is stopping you from doing it. There have been plenty of posts around here on how to set things up the way it used to be pre bookworm.
Plenty of environments out there have always enforced the "though shall not use system's Python anything" and forcing users to use other versions of Python running side by side with the system's going back to Python 2.
What got people in the current "mess" was everyone taking the lazy way out and never learning how to set it all up correctly to begin with. Next thing you know everyone is copying what everyone else is doing because it is easier to copy it than to learn how it works and set it up correctly, and when things change the tiniest but, everyone is throwing their arms into the sky screaming bloody murder.
No offense, but this has more to do with not knowing how it all works than with things being broken.
None of it is rocket science. It is all in the documentation freely available on the web, both in Python's and the distro's repos.
It's pretty simple. Python searches for things in certain paths. Some of the paths have defaults. You can change them, or not, with a handful of environment variables. Or take the other easy way out, use something like Pyenv and run as many versions of Python side by side without one affecting the other, including not touching the system installed interpreter and libs, or use venv's, or a combination of any of them if you wish. It is not a lack of options that is the issue.
It all comes down to PYTHONPATH and sys.path. These things have been a part of Python forever.
The externally-managed-environment has very little with the python team and more so to do with the OS distro maintainers. If you wish it to stay the way it used to be, nothing is stopping you from doing it. There have been plenty of posts around here on how to set things up the way it used to be pre bookworm.
Plenty of environments out there have always enforced the "though shall not use system's Python anything" and forcing users to use other versions of Python running side by side with the system's going back to Python 2.
What got people in the current "mess" was everyone taking the lazy way out and never learning how to set it all up correctly to begin with. Next thing you know everyone is copying what everyone else is doing because it is easier to copy it than to learn how it works and set it up correctly, and when things change the tiniest but, everyone is throwing their arms into the sky screaming bloody murder.
No offense, but this has more to do with not knowing how it all works than with things being broken.
None of it is rocket science. It is all in the documentation freely available on the web, both in Python's and the distro's repos.
It's pretty simple. Python searches for things in certain paths. Some of the paths have defaults. You can change them, or not, with a handful of environment variables. Or take the other easy way out, use something like Pyenv and run as many versions of Python side by side without one affecting the other, including not touching the system installed interpreter and libs, or use venv's, or a combination of any of them if you wish. It is not a lack of options that is the issue.
It all comes down to PYTHONPATH and sys.path. These things have been a part of Python forever.
Statistics: Posted by memjr — Tue Mar 19, 2024 2:33 am