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 nascheme
Recipients docs@python, gregory.p.smith, larry, nascheme
Date 2017-12-20.19:57:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1513799842.32.0.213398074469.issue30492@psf.upfronthosting.co.za>
In-reply-to
Content
Thanks for fixing this.  I always do my builds in subfolders as well.  It is handy to have multiple builds (debug, opt, profiled) that all use a single source tree.

I don't like to hijack this issue but could we get some of the build bots to do their builds in a subfolder?  I don't know who would be able to make that change.  It would be good to smoke out these kinds of problems early.  Otherwise wierdo's like gps and I don't notice them until later.

If we don't keep this working, we should just rip the ability to do builds outside of the source tree out of the Makefile.  There is no point to maintaining the extra complication if it doesn't actually work.  With git shallow clones, I could live with that.  However, it seems a shame to lose it when it basically currently works fine.
History
Date User Action Args
2017-12-20 19:57:22naschemesetrecipients: + nascheme, gregory.p.smith, larry, docs@python
2017-12-20 19:57:22naschemesetmessageid: <1513799842.32.0.213398074469.issue30492@psf.upfronthosting.co.za>
2017-12-20 19:57:22naschemelinkissue30492 messages
2017-12-20 19:57:22naschemecreate