Fuzzyman wrote:
This is really a failing with setuptools of course - which seems to fail to recognise a dependency that isn't installed as an egg. (I eventually solved it by deleting the requirements in the buildutils egg - both kid and docutils were already installed).
At least for Pudge, it should install with setuptools by default. May not, but it should. So if its setup.py is changed, then it will always be okay. That doesn't, however, cover docutils and Kid. Though Kid could probably be changed, it's much more likely someone already has that installed (not nearly so likely that someone has a preexisting installation of Pudge). And docutils is more likely still. This is a bit of a pain, and I don't know what the best resolution is, though I believe setuptools 0.6a8 will better deal with installing an egg when a non-egg is already installed.
FYI, when doing development (and if the setup.py uses setuptools) you can use "python setup.py develop", and then your code will be the live code on the system. This way you don't have to reinstall after you change things. You might already be doing that, but I wasn't sure.
-- Ian Bicking / [EMAIL PROTECTED] / http://blog.ianbicking.org _______________________________________________ Pudge mailing list [EMAIL PROTECTED] http://lesscode.org/mailman/listinfo/pudge
