This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Peter.Waller
Recipients Peter.Waller, alexis, eric.araujo, higery, meatballhat, michael.mulich, tarek
Date 2011-06-16.14:43:29
SpamBayes Score 1.1509048e-09
Marked as misclassified No
Message-id <1308235410.54.0.443416799893.issue8668@psf.upfronthosting.co.za>
In-reply-to
Content
Hi - Great to see this functionality coming. There is one feature of it that I would really like to see fixed, which is currently broken in setuptools/distribute - I'm sorry if this is the wrong forum for this note, but I wanted to add it to the discussion somewhere.

That feature is the "package_dir" argument to setup(). If the sources aren't in the root directory, the package doesn't function correctly with `python setup.py develop`

Here is a reference to an issue filed against distribute:

https://bitbucket.org/tarek/distribute/issue/177/setuppy-develop-doesnt-support-package_dir-arg-to

Is there any possibility of seeing this work correctly? A lot of packages use it, and for them, `develop` is currently broken.

Apologies if this feature is implemented and I missed it, but I see no reference to "package_dir" in the patch, so I would be (pleasantly) surprised if it was implemented. I would be happy to provide a testcase on request.
History
Date User Action Args
2011-06-16 14:43:30Peter.Wallersetrecipients: + Peter.Waller, tarek, eric.araujo, meatballhat, alexis, michael.mulich, higery
2011-06-16 14:43:30Peter.Wallersetmessageid: <1308235410.54.0.443416799893.issue8668@psf.upfronthosting.co.za>
2011-06-16 14:43:29Peter.Wallerlinkissue8668 messages
2011-06-16 14:43:29Peter.Wallercreate