[Distutils] Proposal for incorporating buildout-versions on buildout (Re: Better version pinning in buildout (buildout-versions))

[Benji York]

On Tue, Jan 15, 2013 at 12:21 PM, Eric V. Smith <eric at trueblade.com> wrote:
> On 1/15/2013 6:30 AM, Jim Fulton wrote:
>> On Tue, Jan 15, 2013 at 5:45 AM, Chris Withers <chris at python.org> wrote:
>>> On 15/01/2013 10:36, Jim Fulton wrote:
>>>>>
>>>>> Yeah, I thought it might be this ;-)
>>>>> I don't know how hard it'd be top implement but in an ideal world I'd
>>>>> prefer
>>>>> to see develop eggs trump any other sources but still have version
>>>>> requirements checked.
>>>>
>>>>
>>>> That's the case today.
>>>
>>>
>>> I don't believe it is, if you have:
>>>
>>> [buildout]
>>> develop = /checkouts/somepackage.2.0.0
>>> versions = versions
>>>
>>> [versions]
>>> somepackage = 1.4.2
>>>
>>> ...I've always found that /checkouts/somepackage.2.0.0 isn't on the python
>>> path but that for version 1.4.2 is.
>>
>> Right, meaning the version requirement *is* checked.
>>
>> I guess I don't understand: "I don't know how hard it'd be top
>> implement but in an ideal world I'd prefer to see develop eggs trump
>> any other sources but still have version requirements checked."
>
> I think it means that the develop egg is the only version that's
> considered. If it doesn't match the version requirement, it's an error.

That sounds like a good way to balance the possibility that the develop
egg isn't being used and it is not immediately apparent why not and the
possibility that your stated version requirements are silently not being
met.
-- 
Benji York