versions described about djangorecipe HOT 7 CLOSED

Thank you for taking you time to report this.
Could you please explain why it should display that information?

I've taken some time to look into the way versioning works.
Buildout uses pkg_resources Requirement and works in the same way as
easy_install and pip for versioning.
The version can contain the following: <=, >=, ==, !=, < and >.
django>1.3, django<1.4, django!=1.3 are all valid ways to specify the version.
Unfortunately it's not possible to specify a version range.
So, there is no way to specify the current 1.3.X release branch, except for specifying <1.4.

However the version is mostly used to pin the version. It's up to the developer to test
a new version and use the version pin to upgrade.

from djangorecipe.

How would you say that then? Is the following valid?

[version]
django = >=1.3,<1.3.99

This is valid when specifying eggs versions.

from djangorecipe.

Did you try it to see if it was valid?

from djangorecipe.

it writes django==1.3,<1.3.99 but seem to get indeed the correct version.

from djangorecipe.

I don't know how you used that because I get the following error:
ValueError: ('Expected version spec in', 'django[] === 1.3,<1.3.99', 'at', ' === 1.3,<1.3.99').
As I've said before the only valid version specification is: name, CHAR, version number:
where CHAR is one of <=, >=, ==, !=, < and >.

from djangorecipe.

But that format works for the requirements.txt and the Eggs specification in buildout. Only Django which is in that special [version] section doesn't support it.

from djangorecipe.

Example of a working config:

[buildout]
parts = django
eggs =
    PIL>=1.1.6,<1.1.99
    South>=0.7
    django-mptt-2>=0.3,<0.3.99
    docutils>=0.6
    textile>=2.1,<2.1.99
versions = versions

[versions]
django = 1.3.1

[django]
recipe = djangorecipe
settings = settings_development
eggs = ${buildout:eggs}
project = xxxxx
wsgi = true

from djangorecipe.