[Distutils] "buildout-versions" not showing pinned versions

[Chris Withers]

Hi,

I've CC'ed in the correct mailing list for these discussions, you should 
mail there first in future.

Right, replaying our discussion in it's original order:

 >     On 13/08/2011 04:04, B.Nanda Kishore wrote:
 >
 >         when my buildout.cfg is having content like:
 >         *[buildout]*
 >         *parts = deps*
 >         *extensions = buildout-versions*
 >         *
 >         *
 >         *[deps]*
 >         *recipe = zc.recipe.egg*
 >         *eggs = Django*
 >
 >         and when I run buildout its printing the latest Django 
version(1.3).
 >         Thats fine. But.....
 >         when I pin the version number of Django in buildout.cfg to 
something

Okay, so it looks like you're pinning versions as follows:

On 15/08/2011 06:20, B.Nanda Kishore wrote:
 > Here is my buildout.cfg:
 > [buildout]
 > parts = deps
 > extensions = buildout-versions
 >
 > [deps]
 > recipe = zc.recipe.egg
 > eggs = *Django==1.0.4*

As an aside, I'll point out that the above buildout.cfg doesn't do 
anything useful as Django doesn't expose any setuptools-style console 
scripts.

Now, buildout-versions won't report any versions here since you've 
pinned Django to 1.0.4. It only warns about un-pinned versions of eggs.

Here's a minimal useful recipe that pins Django in a more orthodox 
fashion and provides a bin/py interpreter that will that version 1.0.4 
of django available:

[buildout]
parts = deps
extensions = buildout-versions
versions = versions

[versions]
buildout-versions = 1.6
Django = 1.0.4
setuptools = 0.6c12dev-r88846
zc.buildout = 1.5.2
zc.recipe.egg = 1.3.2

[deps]
recipe = zc.recipe.egg
eggs = Django
interpreter = py

However, I'd suggest looking at the djangorecipe package as a much more 
useful way of dealing with Django in buildout!

cheers,

Chris

-- 
Simplistix - Content Management, Batch Processing & Python Consulting
             - http://www.simplistix.co.uk