On Dec 16, 2012, at 10:10 AM, Wichert Akkerman wrote:
>
> On Dec 14, 2012, at 22:11, Michael Bayer <[email protected]> wrote:
>> But the effect of only publishing 0.8.0b1 on Sourceforge was that I didn't
>> get the impression that we had so many people going out and testing the beta
>> as we normally do. I was reminded by Chris McDonough that a project which
>> really can't afford to jump to 0.8 on an automatic basis should have a
>> requirement set up to keep them on 0.7. So we'll see how it goes -if your
>> project needs to stay on 0.7, *please* set up a requirement for "SQLAlchemy
>> < 0.8" in your requirements.txt and/or install_requires. Otherwise, you'll
>> be a beta tester for 0.8.0b2.
>
> There is a small problem here: 0.8b2 < 0.8 with python's versioning rules.
> There is an alternative spelling though: use "SQLAlchemy < 0.8dev" to make
> sure all pre-releases for 0.8 are also rejected.
For a second there I thought you were talking about using "b2" in the first
place, then I went and sanity checked against pep386 all over again, but you're
talking about the requirement rule - WHEW.
"0.8dev" isn't pep386 compliant:
>>> V('0.8dev') < V('0.8.0b2')
verlib.IrrationalVersionError: 0.8dev
"0.8.dev1" isn't prior to b2:
>>> V('0.8.dev1') < V('0.8.0b2')
False
the best option seems to be "a1":
>>> V('0.8a1') < V('0.8.0b2')
True
http://www.python.org/dev/peps/pep-0386/#the-new-versioning-algorithm
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sqlalchemy?hl=en.
