On 05/04/2013 13:16, Jim Fulton wrote:
The non-develop eggs here have significantly *lower* version numbers.
(and really, if I say I'm developing a package, why would a non-development
version be picked?!)
There are people who agree with you and people who don't.<shrug>
What's your view on it?
My take: how can I ensure that when I put in a develop line, that
package gets used, regardless of the version number, but *especially*
when the version number is greater than other packages found, even if
that version number is a .dev version (which is usually the case..)
Two comments, the first an order of magnitude more important than the
second:
1. I *was using a clean python*. Buildout decided to use some crap *it* left
lying around from a totally different Python installation when I ran
python2.6<clean, build form source> bootstrap.py
But you were using a dirty Python and that left your buildout in a bad
state.
No, I was using a Python that left my buildout in the state any python,
clean or dirty, would have done...
There's not a lot I can (or am willing) to do about that.
Having bootstrap.py really make sure things are started again from
scratch would likely solve all these problems. (The .installed.cfg stuff
I remember hitting before, when only using clean pythons)
Chris
--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
Distutils-SIG maillist - Distutils-SIG@python.org
http://mail.python.org/mailman/listinfo/distutils-sig
