[issue16238] Automatically remove build directory when build options changed

2020-11-06 Thread Éric Araujo
Change by Éric Araujo : -- assignee: eric.araujo -> components: -Distutils versions: -Python 3.8, Python 3.9 ___ Python tracker ___ __

[issue16238] Automatically remove build directory when build options changed

2020-11-06 Thread Irit Katriel
Change by Irit Katriel : -- versions: +Python 3.10, Python 3.8, Python 3.9 -Python 2.7, Python 3.2, Python 3.3 ___ Python tracker ___ _

[issue16238] Automatically remove build directory when build options changed

2012-10-19 Thread Éric Araujo
Éric Araujo added the comment: Right, this is desirable behaviour. I thought setup.py and setup.cfg were dependencies in the files graph, meaning that if setup.py is newer than a py or so/dll file in the build dir, everything gets rebuilt. I’ll have to check that. -- stage: -> test

[issue16238] Automatically remove build directory when build options changed

2012-10-16 Thread Arfrever Frehtes Taifersar Arahesis
Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue16238] Automatically remove build directory when build options changed

2012-10-15 Thread Kushal Das
Changes by Kushal Das : -- nosy: +kushaldas ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue16238] Automatically remove build directory when build options changed

2012-10-15 Thread anatoly techtonik
New submission from anatoly techtonik: After build options in setup.py is edited, command `python setup.py install` doesn't remove build directory and uses its cached content. This behavior is non-obvious and leads to errors. The proposal is to calculate hash from build configuration, save it