[issue32429] Outdated Modules/Setup warning is invisible

Julien Palard added the comment: Fixed in 961d54c5c1916c09883ebcf7191babc969e5a5cf. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue32429] Outdated Modules/Setup warning is invisible

STINNER Victor added the comment: > I'm ok with turning the warning into an error. Does anyone object here? Please don't convert the warning to an error. Usually, I ignore the warning and "make" produces a working ./python binary anyway. It's common that I get the warning when using git bisec

[issue32429] Outdated Modules/Setup warning is invisible

Antoine Pitrou added the comment: I'm ok with turning the warning into an error. Does anyone object here? -- ___ Python tracker ___

[issue32429] Outdated Modules/Setup warning is invisible

Julien Palard added the comment: Discussion about further simplifications goes here: https://bugs.python.org/issue32430 -- ___ Python tracker ___ _

[issue32429] Outdated Modules/Setup warning is invisible

Xavier de Gaye added the comment: 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

Re: [issue32429] Outdated Modules/Setup warning is invisible

On 27.12.2017 00:24, Antoine Pitrou wrote: > > Antoine Pitrou 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-tr

[issue32429] Outdated Modules/Setup warning is invisible

Julien Palard added the comment: > maintain your own branch with changes to a tracked file Make sense for me, Xavier, would this fit your usage? -- ___ Python tracker ___

[issue32429] Outdated Modules/Setup warning is invisible

Antoine Pitrou 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

[issue32429] Outdated Modules/Setup warning is invisible

Julien Palard added the comment: Antoine: I may take a look at this too. Still, stopping in the Makefile looks a first trivial step toward not being screwed by it, removing it looks non trivial, will raise discussions, let's make it another issue? --

[issue32429] Outdated Modules/Setup warning is invisible

Barry A. Warsaw added the comment: On Dec 26, 2017, at 18:17, Antoine Pitrou wrote: > > I'd really like it if we could get rid of the Setup/Setup.dist thing. It's a > distraction to have to type `cp -f Modules/Setup.dist Modules/Setup` from > time to time... even though I have never customi

[issue32429] Outdated Modules/Setup warning is invisible

Antoine Pitrou added the comment: I'd really like it if we could get rid of the Setup/Setup.dist thing. It's a distraction to have to type `cp -f Modules/Setup.dist Modules/Setup` from time to time... even though I have never customized the Setup file. -- nosy: +barry, benjamin.peter

[issue32429] Outdated Modules/Setup warning is invisible

Change by Julien Palard : -- keywords: +patch pull_requests: +4905 stage: -> patch review ___ Python tracker ___ ___ Python-bugs-lis

[issue32429] Outdated Modules/Setup warning is invisible

New submission from Julien Palard : The devguide advise to run `make -j`, why not, but in any cases between `make -j4` and `make -j` the warning: --- Modules/Setup.dist is newer than Modules/Setup; check to make sure you have all the updat