At 12:35 PM 6/7/2006 -0600, Uche Ogbuji wrote:
I can't get setuptools to handle the fact that Amara has all its code in a subdir named lib, such that it used to work fine in plain distutils as follows:
setup(package_dir = {'amara': 'lib'}, packages = ['amara'],...)
This same invocation with setuptools does not give an error message, but no packages are found or processed.
I also tried:
setup(package_dir = {'amara': 'lib'}, packages = find_packages(),
setup(package_dir = {'amara': 'lib'}, packages = find_packages('lib'),
setup(package_dir = {'amara': 'lib'}, packages = find_packages(), packages = ['amara'],
and many other desperate attempts, with no luck.
It feels to me like a bug in setuptools with such a layout, but I'm really surprised, because it's so common,
Actually, it's pretty *un*common, and it's not a good layout to use for many reasons, including non-importability during development, user confusion in understanding the layout, and inconvenience (i.e., a more natural layout wouldn't require setting package_dir at all). Merits of the layout aside, it should nonetheless work properly with setuptools, and I actually didn't have any problems with it. (see further below)
and even covered explicitly by the distutils and setuptools docs.
Actually, setuptools only mentions creating a *parent* package, e.g. package_dir={'':'lib'}, where the 'amara' package directory would then be a subdirectory of lib. Again, however, it *should* work, and as far as I can tell, it does.
cvs -d:pserver:anonymous@cvs.4suite.org:/var/local/cvsroot get Amara
I checked this out, and it builds an egg just fine for me under both 2.3 and 2.4. What problem are you having, exactly?
One last thing: is there an issue tracker for setuptools?
You're speaking to him now. :)