4 ms·
Shipping with python is a disadvantage; any real workflow tool needs to be able to manage multiple python installations, and if you try to use a part of the pyt
by lmm 4y ago
Shipping with python is a disadvantage; any real workflow tool needs to be able to manage multiple python installations, and if you try to use a part of the python installation to do that you've got a circular dependency problem. Plus the whole "where modules go to die" thing.
- solarkraft 4y agoDoes anything speak against flipping the relationship? i.e. using pip (or something else) as the standard way to install Python.
- cdogl 4y agopip is a python program.
- qbasic_forever 4y agoYou might want to look at micromamba as a separate tool that can install python itself, libraries, etc. with zero dependency on a python being installed. It's a very fast tool written in C++ so it's easy to install and use almost anywhere. It uses the conda ecosystem of packages.
- LtWorf 4y agoIf you have multiple versions of python installed you can just do python3.9 -m pip python3.10 -m pip The standard library is the reason why python is popular to begin with.
- Hackbraten 4y agoTo me, that’d be a UX nightmare. Even if I tried to, I’m not going to memorize which of my 20 checked-out Python projects are requiring which Python invocation. IMHO it’s absolutely the toolchain’s job to manage that for me. I’d never adopt a toolchain that wouldn’t.
- LtWorf 4y agoYou do know that python is backwards compatible right? You can just use 3.11 with everything.
- Hackbraten 4y agoIf my project is a library that needs to support e.g. 3.8 through 3.11, then I’m not going to use 3.11 for my development environment. The same goes if my project depends on a library or framework that doesn’t support 3.11.
- lmm 4y agoTraditionally it wasn't, and even a "minor" upgrade was a significant undertaking for a large project. Maybe that's changed.
- mattbillenstein 4y agoMaybe in the 2.4 -> 2.7 transitions - Python3 after about 3.6 is pretty good, you might see some minor package breakage if you're running the very latest version, but that's fairly rare. Generally speaking, if you're on a modern OS - like recent Ubuntu LTS or MacOS you're getting 3.8 -> 3.10 and compatibility is very good in these releases.
- acdha 4y agoWhen exactly are you defining as “traditional”? The Python point releases have generally been painless for a long time. There was a little friction in the early 2-3 era before they made it easier to write code which worked on both without translation but in general it’s been at least a decade since I’ve cared about this except for one time where a couple of libraries depended on a private API which changed in Python 2.7.9, and that was back in 2014. https://bugs.python.org/issue22438 https://bugs.python.org/issue22438