There seems to be a dominant opinion that the file should be on PyPI, and I don't disagree.
One issue is that the file must be mutable. It necessarily contains a reference to the preferred version to be downloaded. That version changes over time. It's typically incremented, but sometimes decremented.
It's possible the script could be updated to otherwise discover the most appropriate version. As it's currently implemented however, the file must be expected to change over time.
Because the file must change during each release, the system needs to be able to accept an updated version. This is why the Bitbucket Link was referenced, because it can include that version information.
I'm open to suggestions on how we can create a perma link to a file that changes over time on PyPI.
For now, the most authoritative place I could think of for that file was the bit bucket downloads. Let's identify a mechanism to do the same on PyPI and get that into set of tools for the next release.
Sent from my comm
On 2013-06-09, at 22:42, "Tres Seaver" firstname.lastname@example.org wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 06/09/2013 10:28 PM, Donald Stufft wrote:
On Jun 9, 2013, at 9:51 PM, Nick Coghlan email@example.com wrote:
On 10 June 2013 03:49, Jason R. Coombs firstname.lastname@example.org wrote:
I'm leaning toward uploading it to BitBucket downloads as part of the release script.
I'll put ez_setup.py for 0.7.2 in downloads for now. You can assume that's where the permalink will be.
I think that's a good way to publish it securely to the PSF infrastructure team (at least for now)
If anyone has a better suggestion, please raise it.
As others have suggested, we should work with Donald and Noah to get the bootstrapping script an official home somewhere on pypi.python.org.
If you want it under pypi.python.org it'll probably need manually sent to myself for the time being. I believe it could easily be hosted via python hosted.org though without needing manual intervention.
I'm not wedded to anyplace in particular. Having the bootstrap needed to make effective use of PyPI hosted on PyPI itself makes a lot of sense to me. Maybe under a URL like this one?
The main key is that the URL should be immutable (so we can doucment it widely, and use it in scripts) and have availability as good as the cheeseshop (I'm not knocking Bitbucket in particular).
If the file were copied into the Sphinx docs uploaded to pythonhosted.org, that would probably work just as well.
=================================================================== Tres Seaver +1 540-429-0999 email@example.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/
iEYEARECAAYFAlG1PO8ACgkQ+gerLs4ltQ64WQCeO0tVhPBjlmzvtzdBx0C4V5Hr lVAAniVJ4XuAnPfV7NXT7KvcextrrTaJ =ILKd -----END PGP SIGNATURE-----
Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig