ulif
commented
8 years ago Fixed metadata of versions that provided a non-PyPI "download_url".
All versions still available, no kitten died.
Closed ulif closed 8 years ago
ulif
commented
8 years ago Fixed metadata of versions that provided a non-PyPI "download_url".
All versions still available, no kitten died.
About three months ago I received an automated message from Donald Stufft, PyPI Administrator, complaining about grokproject hosting project files on non-PyPi servers. If I understand it correctly, this will be forbidden (for PyPI hosted projects) in future according to pep470.
https://pypi.python.org/pypi/pep470
For grokproject I think this is kind of a false alert: in setup.py of some releases we set the 'download_url' parameter to some svn.zope.org address. See for instance
https://pypi.python.org/pypi/grokproject/0.3dev-r73355
where the download url points to svn://svn.zope.org/.. It looks like this (unneeded) URL now triggers the alert for the PyPI maintainers. There might be other Zope projects bitten by similar problems.
I think the setting of "download_url" was not proper. Apparently the complete package was (and is) hosted on PyPI and we used the 'download_url' settings merely to tell where the latest sources can be found. In principle, the download_url could be removed and everything else could be kept as it was.
Unfortunately this does not work with releases as the above, because the version schema is not accepted by PyPI: 0.3dev-r73355 in fact collides with current version numbering. And if I try to change the metadata (including the deleted download_url), all other settings have to meet the PyPI requirements.
So we have to do something else as there is a chance that the complete project will be removed from PyPI otherwise.
Because the troublesome releases seem to be only very old, outdated, and experimental ones, I would like to remove them from PyPI. This would include releases for which
What do others think? Would that be okay?