news
GNU/Linux and More
-
Linux Made Simple ☛ 2025-08-03 [Older] Linux Weekly Roundup #336
-
Instructionals/Technical
-
Distributions and Operating Systems
-
Debian Family
-
-
Free, Libre, and Open Source Software
-
FSFE
-
FSFE ☛ 2025-07-31 [Older] Help the FSFE to connect with representatives [Ed: Microsoft group front]
-
FSFE ☛ 2025-08-06 [Older] MP Explore +++ CRA questionnaire +++ DMA news
-
-
Programming/Development
-
Perl / Raku
-
The Weekly Challenge ☛ 2025-08-06 [Older] Serialisation in Perl
-
The Weekly Challenge ☛ 2025-08-07 [Older] Caching in Perl
-
-
Python
-
University of Toronto ☛ The problem of Python's version dependent paths for packages
A somewhat famous thing about Python is that more or less all of the official ways to install packages put them into somewhere on the filesystem that contains the Python series version (which is things like '3.13' but not '3.13.5'). This is true for site packages, for 'pip install --user' (to the extent that it still works), and for virtual environments, however you manage them. And this is a problem because it means that any time you change to a new release, such as going from 3.12 to 3.13, all of your installed packages disappear (unless you keep around the old Python version and keep your virtual environments and so on using it).
-
-
-