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.10:22:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1500459755.31.0.843629906496.issue29225@psf.upfronthosting.co.za>
In-reply-to
Content
So feel free to close this issue. The use case was quite marginal anyway, and we can always instruct developers to run `build_ext --inplace` when they intend to use the distribution out of the source directory (and not have inplace=1 in setup.cfg, to allow for installation as well).

If anyone should want to try to remove the limitation wrt installation with inplace extensions, I think they're in for quite a bit of work.
History
Date User Action Args
2017-07-19 10:22:35estansetrecipients: + estan, ned.deily, eric.araujo, methane, koobs, dstufft, Elvis Stansvik
2017-07-19 10:22:35estansetmessageid: <1500459755.31.0.843629906496.issue29225@psf.upfronthosting.co.za>
2017-07-19 10:22:35estanlinkissue29225 messages
2017-07-19 10:22:35estancreate