[Zope3-dev] Re: A thought on backward compatibility and minimum versions

[Jim Fulton]

On May 31, 2007, at 11:14 AM, Tres Seaver wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Jim Fulton wrote:
>> On May 31, 2007, at 10:58 AM, Tres Seaver wrote:
>>> I'd rather have the dot, e.g. "foo 2.* >= 2.5", just for clarity:
>>>
>>>   - It makes the intent clearer (that you want any version in the
>>>     "two dot" release line).
>>>
>>>   - It disambiguates the case where the version number might have
>>>     double digits (e.g, '0.1' vs. '0.10').
>>
>> This depends on how the * is interpreted.  setuptools already treats
>> dots as optional in many cases and this would be one more.  I also
>> prefer the last syntax I suggested without the "*". So, the example
>> would become:
>>
>>    "foo 2, >=2.5"
>
> That seems like an empty set to me.

Not to me.  :)  "foo ==2, >=2.5" would be a specification for the  
empty set.

>>> Another feature I'm not sure is already in setuptools:
>>>
>>>   - I *don't* want dev releases to replace production ones
>>>     implicitly:  no package should be able to install a non-released
>>>     version without explicit callout.  If this isn't already the
>>>     default behavior, then I'd like syntax for spelling it.
>>
>> What do you mean by a "dev" release?
>
> Any release tagged as "alpha", "beta", "rc", "pre", or with an SVN  
> revision.

I'm fairly sure that this isn't supported.  It seems like a  
reasonable thing to request.

Jim

--
Jim Fulton			mailto:jim at zope.com		Python Powered!
CTO 				(540) 361-1714			http://www.python.org
Zope Corporation	http://www.zope.com		http://www.zope.org