Elvis Stansvik added the comment: @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. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29225> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
