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 xdegaye
Recipients barry, benjamin.peterson, lemburg, mdk, pitrou, xdegaye
Date 2017-12-27.10:30:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1514370641.52.0.213398074469.issue32429@psf.upfronthosting.co.za>
In-reply-to
Content
It seems that it is possible to keep the current behavior for those that want to customize the configuration of Modules/Setup.dist (knowing that they can just use Modules/Setup.local if they are only doing additions to the Setup configuration) and at the same time get rid of these warnings for those that never change Modules/Setup.dist. This could be done this way:

* 'configure' does not create anymore Modules/Setup.
* The 'Makefile' target of the Makefile uses now Modules/Setup.dist when Modules/Setup is missing.
* A developer that wants to customize Modules/Setup.dist needs to copy (only once) manually Modules/Setup.dist to Modules/Setup and to modify this last file accordingly. She/he gets then the same warnings as those that are occuring currently and in that case it is useful to have the build abort upon such warnings as proposed in the current issue.

If this proposal is acceptable then it should be implemented in another issue, I think.
History
Date User Action Args
2017-12-27 10:30:41xdegayesetrecipients: + xdegaye, lemburg, barry, pitrou, benjamin.peterson, mdk
2017-12-27 10:30:41xdegayesetmessageid: <1514370641.52.0.213398074469.issue32429@psf.upfronthosting.co.za>
2017-12-27 10:30:41xdegayelinkissue32429 messages
2017-12-27 10:30:41xdegayecreate