6 ms·
It's impressive how my pip version seems to always be out of date.
by st1x7 6y ago
It's impressive how my pip version seems to always be out of date.
- tsjq 6y ago;-)
- asah 6y agoIn all seriousness, the constant warnings mean that users may ignore serious upgrades.
- mehrdadn 6y agoNo kidding. I pretty much don't even believe in the concept of a serious upgrade anymore, as far as pip goes anyway. As long as it still works when I run it, nobody is missing out on any serious upgrades as far as I'm concerned at this point.
- belval 6y agoThat's a pretty bad mindset, new pip versions (20+) include support for binary distributions that saves a lot of time when installing pretty much anything that needs to be compiled. Just run `pip install --upgrade pip` every month and you will be fine.
- hobofan 6y agoDo you have a reference for that? IIRC binary wheels have been supported for ages and not just in 20+ (which was released this year).
- dralley 6y agoWhat the likely mean, is that newer versions of pip support newer platforms underpinning the binary packages. Python binary packages are a bit of a kludge, they take a binary built on a base platform like CentOS 5, and use tools like patchelf to take all the libraries that they dynamically link against and re-wrap them in a new package. Until about a year ago, CentOS 5 was the newest base platform available. So if your library needed a glibc feature or some other library feature from the past decade you were SoL.
- asah 6y agothx - this is actually v helpful to me. yay for HN!
- mehrdadn 6y agoI'm not sure what you're talking about (pip's always done binaries for me), but I have 20.1 in any case, so...
- tsjq 6y agoFully agree with this. That line has become "invisible" to my brain.
- simlevesque 6y agoexcept if the command fails, then I upgrade.
- danpalmer 6y agoIn my experience this is less to do with the fast pace of development, and more to do with the fact that many engineers use virtualenvs, and virtualenvs "vendor" the pip version so you need to update pip in each virtualenv you use. This is correct, but does lead to needing to upgrade so much.
- mkl95 6y ago20 versions are no joke. I can't remember the last time I used a command that wasn't install, but I suppose they are no joke! On the other hand I would love to use the shiny new feature, but explaining it to my manager would be like talking to a tree.
- FerretFred 6y agoIt looks version 21 (!) will remove support for Python 2.7 - now that should be interesting...
- mkl95 6y agoInteresting! A local company tried to hire me months ago to migrate a 2.6 legacy system to bleeding edge 2.7, I wonder if they have convinced someone yet.
- JshWright 6y agoWere there any backwards incompatible changes in 2.7? I'm trying to remember if I even noticed when that version bump happened...
- mkesper 6y agoYes, try to install it on a CentOS6 box as /usr/bin/python and suddenly no more yum etc. will work.
- toyg 6y agoRelease notes: http://hg.python.org/cpython/raw-file/v2.7/Misc/NEWS http://hg.python.org/cpython/raw-file/v2.7/Misc/NEWS TBH I think the main thing about that release, for me, was the introduction of context managers ("with"). I don't remember any particular breakage but I wasn't doing sysadmin at the time, maybe there is something in the bowels of redhat that relied on some broken behaviour...
- takeda 6y ago2.7 was essentially a bridge to Python 3. All features it has were backported from 3. This is why so many people before 2015 were saying that Python 3 doesn't provide any new features.
- mehrdadn 6y agoI swear... it is so incredibly frustrating that I want to punch my computer when I see that message at this point. I think I had to finally shut it up via https://stackoverflow.com/a/64853362 https://stackoverflow.com/a/64853362 to get my blood pressure to finally drop.
- deleted 6y ago[deleted]