this post was submitted on 24 Aug 2023
1 points (100.0% liked)
Technology
50 readers
1 users here now
This magazine is dedicated to discussions on the latest developments, trends, and innovations in the world of technology. Whether you are a tech enthusiast, a developer, or simply curious about the latest gadgets and software, this is the place for you. Here you can share your knowledge, ask questions, and engage in discussions on topics such as artificial intelligence, robotics, cloud computing, cybersecurity, and more. From the impact of technology on society to the ethical considerations of new technologies, this category covers a wide range of topics related to technology. Join the conversation and let's explore the ever-evolving world of technology together!
founded 2 years ago
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Miniconda drives me crazy and the one time I tried to use it, it changed my default python environment system-wide. I have been increasingly annoyed by Python's having so absurdly many fractional versions, and its scripts refusing to work unless you supply them with version N.nnnn.nnn exactly. (Yes, I am exaggerating.) Here is the acceptable pace to make incompatible versions of a programming language: no more than every 2 years.
Yup, packaging is the worst side of python. Conda having a default base environment is a huge mistake on their part, many people are burned by this constantly. I suggest you try mamba/micromamba: it's the same, much faster, and has no base env by default.
Btw, python hasn't had backward incompatibe versions for more than a decade now. The problem comes from libraries being too strict or too loose with their restrictions, with at the same time no way for the interpreter to simply use different versions of the same library at once (which other languages like julia can do)