[issue6954] DISTUTILS_DEBUG causes stack trace, really simple fix

Tarek Ziadé added the comment: Everything is covered now, and the mentioned bug is fixed in trunk (r74994), py3k (r74999) and release31 (75000). Thanks ! -- status: open -> closed ___ Python tracker _

[issue6954] DISTUTILS_DEBUG causes stack trace, really simple fix

Changes by Tarek Ziadé : -- versions: +Python 2.7 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue6954] DISTUTILS_DEBUG causes stack trace, really simple fix

Tarek Ziadé added the comment: Mmm, the problem is deeper for the second stack trace: distutils.fancy_getopt.longopt_xlate was changed from a translation mapping into a lambda in py3, that's why you have it. I'm fixing back this problem too. -- versions: +Python 3.2

[issue6954] DISTUTILS_DEBUG causes stack trace, really simple fix

Tarek Ziadé added the comment: Thanks for noticing this. I'll add some test covering these and fix the problems. -- priority: -> normal resolution: -> accepted ___ Python tracker _

[issue6954] DISTUTILS_DEBUG causes stack trace, really simple fix

Ned Batchelder added the comment: Another one: Traceback (most recent call last): File "setup.py", line 72, in **addl_args File "c:\python31\lib\distutils\core.py", line 149, in setup dist.run_commands() File "c:\python31\lib\distutils\dist.py", line 919, in run_commands self

[issue6954] DISTUTILS_DEBUG causes stack trace, really simple fix

New submission from Ned Batchelder : If you set the environment variable DISTUTILS_DEBUG=1, distutils will run with DEBUG, which will trace internal activity. But one of the traces is incorrect, and leads to this stack trace: Traceback (most recent call last): File "setup.py", line 116, in