On Tue, Jan 15, 2013 at 1:22 AM, Chris Withers <chris@python.org> wrote:
On 13/01/2013 03:43, Marius Gedminas wrote:
4. Change: develop eggs found in the buildout's develop-eggs directory will be used even if their version conflicts with a pinned version.
Did somebody ask for this?
I believe I mentioned this.
I used to trip on this gotcha practically every time:
- work on package foo that depends on bar - discover a bug in bar that manifests when I use it from foo - check out bar from svn trunk - add a 'mg.cfg' in foo's source tree with [buildout] extends = buildout.cfg develop = ../bar - bin/buildout -c mg.cfg - try some import pdb; pdb.set_trace() or debug prints in ../bar/src/..., run a project in foo, wonder why the breakpoints/debug prints won't work, check bin/runfoo, see ~/.buildout/eggs/bar-1.2.3.egg in there, realize what's the matter - edit mg.cfg again, add [versions] bar = - run bin/buildout -c mg.cfg again, continue debugging.
It's an unnecessary speedbump.
Yeah, I thought it might be this ;-) I don't know how hard it'd be top implement but in an ideal world I'd prefer to see develop eggs trump any other sources but still have version requirements checked.
That's the case today. So why did you change this in buildout-versions? (Or did you?) The buildout-versions docs only say that unpinned versions aren't reported for develop-eggs. They don't actually say that version requirements are ignored for develop eggs. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton Jerky is better than bacon! http://zo.pe/Kqm