3 ms·

edit: wrongness

• dragonwriter 6y ago
  > New deployments will break once pip is updated. No, they won't. > The error here is you think the people doing this even have programmers to port to 3.x or admins with the wherewithal to make sure an older version of pip is used. What wherewithal does that take? PyPI will just provide the last version of pip that supports Python 2. It takes no extra effort to not install a Python 3 version of pip on Python 2. > Nobody wants to keep Python 2.x in use or force the Pip maintainers to keep 2.x support. I'm sure there are people who do want to do the former. And they can, but it has no bearing on the latter.
  • 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 ago
        Thanks!
      • _flux 6y ago
        But 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 ago
          Well, 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.