[issue8101] w32-shared-ptr.c assertion on Windows 7 with 2.6.4

Ned Batchelder ned...@users.sourceforge.net added the comment: Yup, you're both right! I had a C extension (for coverage.py) built for 2.5 in the 2.6 path. Sorry for the false alarm. -- status: open - closed ___ Python tracker rep

[issue6954] DISTUTILS_DEBUG causes stack trace, really simple fix

New submission from Ned Batchelder ned...@users.sourceforge.net: 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

[issue6954] DISTUTILS_DEBUG causes stack trace, really simple fix

Ned Batchelder ned...@users.sourceforge.net added the comment: Another one: Traceback (most recent call last): File setup.py, line 72, in module **addl_args File c:\python31\lib\distutils\core.py, line 149, in setup dist.run_commands() File c:\python31\lib\distutils\dist.py, line

[issue6359] pyexpat.c calls trace function incorrectly for exceptions

New submission from Ned Batchelder ned...@users.sourceforge.net: Pyexpat.c calls the tracing function explicitly (not sure why). When it intercepts an exception, it calls the function with PyTrace_EXCEPTION, but then leaves the scope without calling PyTrace_RETURN. This is incorrect

[issue2506] Line tracing of continue after always-taken if is incorrect

Ned Batchelder [EMAIL PROTECTED] added the comment: It's hard for me to agree with your assessment that for no practical good would come from disabling the optimizer. Broadly speaking, there are two types of code execution: the vast majority of the time, you execute the code so that it can do

[issue2506] Line tracing of continue after always-taken if is incorrect

Ned Batchelder [EMAIL PROTECTED] added the comment: Raymond, do you have a cannon-less recommendation of how to kill this particular mosquito? __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2506

[issue2516] Instance methods are misreporting the number of arguments

Changes by Ned Batchelder [EMAIL PROTECTED]: -- nosy: +nedbat __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2516 __ ___ Python-bugs-list mailing list Unsubscribe

[issue2506] Line tracing of continue after always-taken if is incorrect

New submission from Ned Batchelder [EMAIL PROTECTED]: When tracing line execution with sys.settrace, a particular code structure fails to report an executed line. The line is a continue statement after an if condition in which the if condition is true every time it is executed. Attached

[issue2506] Line tracing of continue after always-taken if is incorrect

Ned Batchelder [EMAIL PROTECTED] added the comment: I see that the cause of the problem is the peephole optimizer. That doesn't mean this isn't a problem. I am measuring the code coverage of a set of tests, and one of my lines is being marked as not executed. This is not the fault

[issue2506] Line tracing of continue after always-taken if is incorrect

Ned Batchelder [EMAIL PROTECTED] added the comment: I recognize that this is an unusual case, but it did come up in the real world. I found this while measuring test coverage, and the continue line was marked as not executed, when it was. I don't understand when the peepholer is moved, so

<    1   2   3   4