3 ms·
It sounds like all you needed was a newer version. Most distributions deliberately try to ship a version that was current at the time of release and don't updat
by rlpb 10y ago
It sounds like all you needed was a newer version. Most distributions deliberately try to ship a version that was current at the time of release and don't update it later except for bugfixes. This is for the user stability reason I gave above. This is what a distribution release is, and why many Ubuntu users prefer the LTS release over every six-monthly release.
If this is the case here, then this isn't a Python-specific problem at all. Developers have a choice: use the chosen distribution release version, or if that's not new enough, then find another way. For Python, one (commonly accepted and good) answer happens to be virtualenv. Many choose, because of their particular circumstances, to go all virtualenv and ignore distribution packages altogether.
Can I guess that you used an Ubuntu LTS, so you effectively opted in to packages that are older but don't change often?
Some solve this by never using a distribution version at all, which is fine. But understand that this is the nature of what a distribution is, and applies to the entire ecosystem, not just the Python one.
- Eridrus 10y agoIt's possible I had an old version, but I was trying to do super basic things with PIL on 14.04 LTS; literally just cropping a JPEG and things were failing. Do I have this problem in Java/Node/Go/Rust? No, I don't. The reason I don't have this problem is that dependencies are not installed globally, they are defined per-project and often statically linked in, there is no such thing as a conflict between two of those projects.
- rlpb 10y ago> It's possible I had an old version, but I was trying to do super basic things with PIL on 14.04 LTS; literally just cropping a JPEG and things were failing. It sounds to me that you hit some kind of straightforward bug then, rather than some systemic issue.