3 ms·
Why won’t new deployments break? If they are using ‘pip’ to install 2.x libraries, my understanding is it will now fail.
by ianhanschen 6y ago
Why won’t new deployments break? If they are using ‘pip’ to install 2.x libraries, my understanding is it will now fail.
- deleted 6y ago[deleted]
- dragonwriter 6y ago> Why won’t new deployments break? Because the bundled pip with Python 2 is py2 compatible, and upgrading it from pyPI will get the last version that supports py2. If you are using distro packages, no distro that packages py2 is going to package anything but a py2-compatible pip tied to it. All this means is that there will be no new versions of pip for py2.
- ianhanschen 6y agoThanks!
- _flux 6y agoBut then at some point a breaking change in the backing service could be introduced, thus breaking pip2. Distros providing pip2 as part of their LTS will probably backport such changes.
- dragonwriter 6y agoWell, yes, it's possible some future change to pyPI could break pip, but that would also break all versions of pip before the change, so there'd have to be a large transition window (because pyPI is how you update pip, too, so if you break existing clients, no one can get the upgrade to the version that supports the backend changes), so that's not going to be sudden and without warning.