[py-dev] setup.py broken in develop mode on trunk
Hi there, In order to see whether a bugfix in Py trunk fixed a bug in my project, I tried installing the py trunk as a develop egg (using buildout). It's possible "python setup.py develop" is therefore similarly broken. I see files mentioned in MANIFEST which don't exist, so initially I thought this was blocking things. It turns out however that setup.py has references to packages which at least don't appear to exist: py.io.test, py.test.rsession, py.test.terminal. After I remove those from setup.py things seem to work again (that is, I can run the code. I get errors. Another mail about those...) With setuptools, MANIFEST shouldn't be necessary: you can instruct setup.py to automatically assume files that are checked into SVN are in manifest, with something like this: from setuptools import find_packages package_dir={'': 'src'}, packages=find_packages('py'), Regards, Martijn
Hi there, Attached is a hacky patch to setup.py which makes buildout develop mode (and quite possibly also "python setup.py develop", but I know buildout better) happy for the trunk. I just removed anything that tripped up running setup.py. Regards, Martijn
Hi Martijn, thanks for noting ... On Tue, Aug 19, 2008 at 18:46 +0200, Martijn Faassen wrote:
In order to see whether a bugfix in Py trunk fixed a bug in my project, I tried installing the py trunk as a develop egg (using buildout). It's possible "python setup.py develop" is therefore similarly broken.
I see files mentioned in MANIFEST which don't exist, so initially I thought this was blocking things. It turns out however that setup.py has references to packages which at least don't appear to exist: py.io.test, py.test.rsession, py.test.terminal. After I remove those from setup.py things seem to work again (that is, I can run the code. I get errors. Another mail about those...)
... and sorry for the confusion. Actually the setup.py on py/trunk resulted from a yesterday merge of release/0.9.x ... but i now regenerated the setup.py and MANIFEST files.
With setuptools, MANIFEST shouldn't be necessary: you can instruct setup.py to automatically assume files that are checked into SVN are in manifest, with something like this:
from setuptools import find_packages
package_dir={'': 'src'}, packages=find_packages('py'),
ok, but for now i'd still like to be compatible to distutils (a user can just switch a "1" to "0") and i am auto-generating the setup.py file so i don't care. let me know if the problems persist or things just work. holger
participants (2)
-
holger krekel -
Martijn Faassen