[issue10374] distutils[2] should recreate scripts in the build tree

2021-02-03 Thread Steve Dower
Steve Dower added the comment: Distutils is now deprecated (see PEP 632) and all tagged issues are being closed. From now until removal, only release blocking issues will be considered for distutils. If this issue does not relate to distutils, please remove the component and reopen it. If

[issue10374] distutils[2] should recreate scripts in the build tree

2019-03-15 Thread Mark Lawrence
Change by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue10374] distutils[2] should recreate scripts in the build tree

2014-07-06 Thread Mark Lawrence
Mark Lawrence added the comment: I always find distutils anything but easy :) -- components: -Distutils2 nosy: +BreamoreBoy, dstufft versions: +Python 3.4, Python 3.5 -3rd party, Python 2.7, Python 3.2, Python 3.3 ___ Python tracker

[issue10374] distutils[2] should recreate scripts in the build tree

2012-05-16 Thread Éric Araujo
Éric Araujo mer...@netwok.org added the comment: In distutils2, 99382aafa4c5 forces scripts to always be rebuilt and 463d3014ee4a goes further and deletes the whole build dir to avoid installing scripts built from a previous build call with a different configuration (i.e. different list of

[issue10374] distutils[2] should recreate scripts in the build tree

2012-03-27 Thread Éric Araujo
Éric Araujo mer...@netwok.org added the comment: I now think that this should be fixed in d1 too. We could just always rebuild scripts (it’s just a file copy), or implement the matching idea from my previous message. To answer my own question: Or is there a rule that says build_* command