Its not just with Django. I have faced the same problem with a different custom package <div>also. I have developed two sample packages(having just a setup.py with name and version mentioned)</div><div>and I have tried installing both those packages using buildout. One of those packages version number is pinned.</div>
<div>Here is the buildout.cfg</div>
<div><br></div><div><div><font size="4">[buildout]</font></div><div><font size="4">index=<a href="http://localhost:8000/" target="_blank">http://localhost:8000/</a></font></div><div><font size="4">parts = deps</font></div>
<div><font size="4">extensions = buildout-versions</font></div><div><font size="4"><br></font></div><div><font size="4">[deps]</font></div><div><font size="4">recipe = zc.recipe.egg</font></div>
<div><font size="4">eggs = PkgA</font></div><div><font size="4"> PkgB==0.1.0</font></div></div><div><font size="4"><br></font></div><div>
When I ran the buildout, this is the output I got.</div><div><br></div><div><div style="font-size:large">[versions]</div><div style="font-size:large">PkgA = 0.1.0</div><div style="font-size:large">buildout-versions = 1.6</div>
<div style="font-size:large">distribute = 0.6.19</div><div style="font-size:large">zc.buildout = 1.5.2</div><div style="font-size:large">zc.recipe.egg = 1.3.2</div><div style="font-size:large"><br></div><div>Notice that PkgB's version is not printed. My doubt was regarding the</div>
<div>Line#33 in <a href="https://github.com/Simplistix/buildout-versions/blob/master/src/buildout_versions/__init__.py#L33" target="_blank">buildout-versions/__init__.py</a>. That is the one which is filtering</div><div>
the pinned distributions. I wanted to know why is it doing it ?</div>
<div><br></div></div><div>Regards,<br>Nandakishore<br>
<br><br><div class="gmail_quote">On Tue, Aug 16, 2011 at 8:20 PM, Chris Withers <span dir="ltr"><<a href="mailto:chris@simplistix.co.uk" target="_blank">chris@simplistix.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
I've CC'ed in the correct mailing list for these discussions, you should mail there first in future.<br>
<br>
Right, replaying our discussion in it's original order:<div><br>
<br>
> On 13/08/2011 04:04, B.Nanda Kishore wrote:<br>
><br>
> when my buildout.cfg is having content like:<br>
> *[buildout]*<br>
> *parts = deps*<br>
> *extensions = buildout-versions*<br>
> *<br>
> *<br>
> *[deps]*<br>
> *recipe = zc.recipe.egg*<br>
> *eggs = Django*<br>
><br>
> and when I run buildout its printing the latest Django version(1.3).<br>
> Thats fine. But.....<br>
> when I pin the version number of Django in buildout.cfg to something<br>
<br></div>
Okay, so it looks like you're pinning versions as follows:<div><br>
<br>
On 15/08/2011 06:20, B.Nanda Kishore wrote:<br>
> Here is my buildout.cfg:<br>
> [buildout]<br>
> parts = deps<br>
> extensions = buildout-versions<br>
><br>
> [deps]<br>
> recipe = zc.recipe.egg<br></div>
> eggs = *Django==1.0.4*<br>
<br>
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.<br>
<br>
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.<br>
<br>
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:<div><br>
<br>
[buildout]<br>
parts = deps<br>
extensions = buildout-versions<br></div>
versions = versions<div><br>
<br>
[versions]<br>
buildout-versions = 1.6<br></div>
Django = 1.0.4<br>
setuptools = 0.6c12dev-r88846<div><br>
zc.buildout = 1.5.2<br>
zc.recipe.egg = 1.3.2<br>
<br></div><div>
[deps]<br>
recipe = zc.recipe.egg<br>
eggs = Django<br></div>
interpreter = py<br>
<br>
However, I'd suggest looking at the djangorecipe package as a much more useful way of dealing with Django in buildout!<div><div></div><div><br>
<br>
cheers,<br>
<br>
Chris<br>
<br>
-- <br>
Simplistix - Content Management, Batch Processing & Python Consulting<br>
- <a href="http://www.simplistix.co.uk" target="_blank">http://www.simplistix.co.uk</a><br>
</div></div></blockquote></div><br></div>