At 08:16 AM 4/10/2011 +1000, Richard Jones wrote:
On Sun, Apr 10, 2011 at 5:12 AM, P.J. Eby <[email protected]> wrote:
> At 09:13 AM 4/9/2011 +1000, Richard Jones wrote:
>> On Sat, Apr 9, 2011 at 8:57 AM, Tres Seaver <[email protected]> wrote:
>> >I also don't know
>> > whether it [setuptools] scrapes VCS URLs from the '/simple' interface.
>>
>> Oh gods I hope not.
>
> Um, that's a big part of what the /simple interface is *for*, so it doesn't
> have to pull them from the formatted HTML of the /pypi interface.
Just to be clear: the VCS URL is only ever used in the absence of any
other (suitable) package files?
URLs are used when they match the criteria given by the user.
If they put it on the command line explicitly, it gets used. If it's
an obvious distribution filename at the end of the URL, the version
info is used to determine whether it's relevant.
Otherwise, it has to have a '#egg' tag to indicate what project and
version the link is for... and then it'll get used if it matches the
version spec that's being searched for.
Usually, an SVN or other revision control link is going to have an
'#egg=myproject-dev' tag, meaning "this is a URL for version 'dev' of
'myproject'", so it'll only be downloaded if it's the only link, OR
if the user explicitly requests a version matching 'dev', and there's
nothing with a higher version to match.
That's my reading of
http://peak.telecommunity.com/DevCenter/EasyInstall#downloading-and-installing-a-package
The doc you want for that is this one, actually:
http://peak.telecommunity.com/DevCenter/setuptools#making-your-package-available-for-easyinstall
_______________________________________________
Catalog-SIG mailing list
[email protected]
http://mail.python.org/mailman/listinfo/catalog-sig
