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 estan
Recipients Elvis Stansvik, dstufft, eric.araujo, estan, koobs, methane, ned.deily
Date 2017-07-19.09:17:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1500455869.68.0.0947296596173.issue29225@psf.upfronthosting.co.za>
In-reply-to
Content
@inada.naoki: I was half afraid that note in the docs would be brought up :) But I should have brought it up myself, sorry about that.

My take is that I see no reason why this limitation should exists. For projects that have extensions, and wish to be runnable both directly from the distribution source tree, but also be installable, it would be quite convenient to be able to set inplace=1 in setup.cfg and have it just work (tm). At least, that's how I ran into this issue. Doing so breaks `setup.py install`.

I haven't tested other targets like sdist and bdist_wheel, but I'll do that and report back.
History
Date User Action Args
2017-07-19 09:17:49estansetrecipients: + estan, ned.deily, eric.araujo, methane, koobs, dstufft, Elvis Stansvik
2017-07-19 09:17:49estansetmessageid: <1500455869.68.0.0947296596173.issue29225@psf.upfronthosting.co.za>
2017-07-19 09:17:49estanlinkissue29225 messages
2017-07-19 09:17:49estancreate