[Grok-dev] Re: solving buildout problems - pinning down eggs

Martijn Faassen faassen at startifact.com
Fri Sep 14 11:00:15 EDT 2007

Brandon Craig Rhodes wrote:
> Martijn Faassen <faassen at startifact.com> writes:
>> We need to have, and use, the facility to "pin down" Grok's
>> dependencies to specific version numbers.  This means we need to
>> produce a complete list of *all* of the egg versions that grok is
>> using.
> That won't break things even more often?  I thought that PyPI by
> default removed access to old versions of a product once a new one was
> submitted - or, since all Grok dependencies are either our packages or
> those of the Zope 3 project, are we trusting them to upload correctly
> and leave old versions accessible?

No, the older versions are still accessible by default as far as I'm 
aware. Anyway, it'd be really bad that as soon as, say, lxml 2.0alpha 
was submitted, lxml 1.3 is inaccessible, right?



More information about the Grok-dev mailing list