On 02/06/2017 12:24 AM, Thomas Bechtold wrote:
Hi,
On Sun, 2017-02-05 at 19:33 +0100, Axel Braun wrote:
Am Sonntag, 5. Februar 2017, 13:12:18 CET schrieb Mikhail Terekhov:
Hi,
There are at least three ways to use PyPI as a source URL for python packages:
https://pypi.python.org/pypi - a canonical (production) site
https://pypi.org - a pre production (test) version of the Warehouse that according its documentation will _eventually_ power the canonical site.
https://pypi.io - just redirects to https://pypi.org
I noticed that pypi.io points to files.pythonhosted.org ...so this would be #4
In a declined request the python maintainers asked to point to pypi.io, without answering why any of the other options is 'invalid'.
I've also had a declined request to update the source url with pypi.io for a new Python package.
pypi.python.org is "invalid" because it has only hashed urls so you need to update the Source url whenever you update the version. See [1]. So I personally prefer pypi.io because it is short. But I'm also fine with option 2 and 4.
Best
Tom
[1] https://bitbucket.org/pypa/pypi/issues/438/backwards-compatible-un- hashed-package
The maintainer who made the url changes [1] recommends files.pythonhosted.org. It has one less redirect than pypi.io. The Python packaging documentation [2] mentions py2pack using pypi.python.org. And it indeed generates the spec using the hashed url. [1] https://bitbucket.org/pypa/pypi/issues/438/backwards-compatible-un-hashed-pa... [2] https://en.opensuse.org/openSUSE:Packaging_Python -- Sean Marlow Public Cloud Developer sean.marlow@suse.com -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org