On Jun 10, 2013, at 2:55 PM, "Jason R. Coombs" <jar...@jaraco.com> wrote:
> 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. Put a version in the filename/path, and have a "latest" tag that just 301 redirects to whatever is latest. /bootstrap/setuptools/latest/ez_setup.py -> 301 Redirect to /bootstrap/setuptools/0.7.2/ez_setup.py > > 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 ----------------- Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
