On 27.12.2017 00:24, Antoine Pitrou wrote: > > Antoine Pitrou <pit...@free.fr> added the comment: > >> +1 - do you have any thoughts on that? > > I think the current scheme may have been useful at a time where DVCS didn't > exist. You would maintain an unversioned copy of Modules/Setup.dist in your > work-tree. Nowadays you can fork a github repo and maintain your own branch > with changes to a tracked file. I don't think Modules/Setup deserves special > treatment compared to, say, setup.py or Makefile.pre.in.
The file is mostly meant for people using tar balls rather than checkouts to give them an easy way back to default settings after making changes to the Modules/Setup file. The same could be had by having Makefile.pre.in generate Setup.dist from Setup while booting into build mode, avoiding the need to sometimes create Modules/Setup manually. -- Marc-Andre Lemburg eGenix.com _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
