On Tue, Dec 18, 2018 at 3:43 PM Tzu-ping Chung <uranu...@gmail.com> wrote:
> Paul has described the technical details behind this phenomenon, but > to be more explicit: it is not pip that breaks older packages, but the > new PyPI server (pypi.org instead of the old pypi.python.org) that does. > > So no, there is not a legacy mode in pip. Furthermore, you won’t be > able to install the package now, even if you have the old pip version. > > The only way to overcome this is to find the original package, and > either upload it to PyPI, or serve it yourself on your own server. > When dealing with legacy setups, buildout still has most of the required machinery to make arcane things tick. If the file still exists, buildout can be configured to follow the links via explicit whitelisting of acceptable sources (and many a links of the bitrot variety are still available through being a tad lucky through archive.org - pre-stdlib inclusion elementtree eggs are a fine example of this). http://www.buildout.org/en/latest/reference.html#buildout-configuration-options The real solution is to dive in to maintain the package barely enough to upload a new release to PyPI, though. -- Joni Orponen
-- Distutils-SIG mailing list -- distutils-sig@python.org To unsubscribe send an email to distutils-sig-le...@python.org https://mail.python.org/mm3/mailman3/lists/distutils-sig.python.org/ Message archived at https://mail.python.org/archives/list/distutils-sig@python.org/message/UR446SHJO2M4FNCIYEQAN3YKQMSH3GRJ/
