You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It used to be that pypi had urls for files that followed predictable a predictable pattern. Specifically, the download was of the form http://pypi.python.org/packages/source/{first letter of package name}/{package name}/{file name}. This made it great for automated validation and downloads, since once you got the pattern it would work for all future versions. The current file names, however, don't have any obvious pattern, instead using some sequence of characters like https://files.pythonhosted.org/packages/ae/98/3b27e0a3c53ec0d6727eb19da46eed5705fa9250ed28ec0d1df48778c401/Django-1.10a1.tar.gz. I think for third-party tools having a simple, predictable file name would be really helpful. It wouldn't have to be the same pattern, but something that follows a consistent, predictable pattern.
The text was updated successfully, but these errors were encountered:
It used to be that pypi had urls for files that followed predictable a predictable pattern. Specifically, the download was of the form
http://pypi.python.org/packages/source/{first letter of package name}/{package name}/{file name}
. This made it great for automated validation and downloads, since once you got the pattern it would work for all future versions. The current file names, however, don't have any obvious pattern, instead using some sequence of characters likehttps://files.pythonhosted.org/packages/ae/98/3b27e0a3c53ec0d6727eb19da46eed5705fa9250ed28ec0d1df48778c401/Django-1.10a1.tar.gz
. I think for third-party tools having a simple, predictable file name would be really helpful. It wouldn't have to be the same pattern, but something that follows a consistent, predictable pattern.The text was updated successfully, but these errors were encountered: