| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
propagating exceptions.
|
| |
|
|
| |
context manager's __exit__ method's result while it's being converted to bool.
|
| | |
|
| |
|
|
|
|
| |
Fixes Issue #874900: after an os.fork() call the threading module state is cleaned
up in the child process to prevent deadlock and report proper thread counts
if the new process uses the threading module.
|
| | |
|
| |
|
|
| |
This is a backport of r65005.
|
| |
|
|
|
|
| |
whose write() method installs another sys.stdout.
Backport of r64633
|
| | |
|
| | |
|
| |
|
|
|
|
| |
conditions in the PyOS_vsnprintf C API function.
This is a backport of r63728 and r63734 from trunk.
|
| |
|
|
|
|
|
|
| |
another class.
Test is run with "regrtest.py -R:: test_compile"
Backport of r62015
|
| |
|
|
| |
and **kwargs expressions could give bogus error messages.
|
| | |
|
| |
|
|
|
| |
only available if asserts are left in the code, in cases where they
can't be triggered from Python code.
|
| |
|
|
|
|
| |
r60579 broke a test test_compile, which seems to test an "implementation detail" IMO.
Also test that this correction does not impact the debugger.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
iteration of a while statement.
The mapping between bytecode offsets and source lines (lnotab) did not contain
an entry for the beginning of the loop.
Now it does, and the lnotab can be a bit larger:
in particular, several statements on the same line generate several entries.
However, this does not bother the settrace function, which will trigger only
one 'line' event.
The lnotab seems to be exactly the same as with python2.4.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
optimized the
whole construct away, even when an 'else' clause is present::
while 0:
print("no")
else:
print("yes")
did not generate any code at all.
Now the compiler emits the 'else' block, like it already does for 'if' statements.
Backport of r60265.
|
| | |
|
| | |
|
| |
|
|
| |
PyArgs_ParseTuple t# and w# formats truncated the lengths to 32bit.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When an unfinished generator-iterator is garbage collected, PyEval_EvalFrameEx
is called with a GeneratorExit exception set. This leads to funny results
if the sys.settrace function itself makes use of generators.
A visible effect is that the settrace function is reset to None.
Another is that the eventual "finally" block of the generator is not called.
It is necessary to save/restore the exception around the call to the trace
function.
This happens a lot with py3k: isinstance() of an ABCMeta instance runs
def __instancecheck__(cls, instance):
"""Override for isinstance(instance, cls)."""
return any(cls.__subclasscheck__(c)
for c in {instance.__class__, type(instance)})
which lets an opened generator expression each time it returns True.
And the problem can be reproduced in 2.5 with pure python code.
|
| |
|
|
|
| |
Fix Coverity 185-186: If the passed in FILE is NULL, uninitialized memory
would be accessed.
|
| |
|
|
| |
Fix Coverity #158: Check the correct variable.
|
| |
|
|
| |
(backport from rev. 58204)
|
| | |
|
| | |
|
| |
|
|
|
| |
Backport from py3k rev. 55708 by Guido.
(backport from rev. 55802)
|
| |
|
|
| |
(backport from rev. 55732)
|
| | |
|
| |
|
|
|
|
| |
lack of an infinite recursion check.
Contributed by Damien Miller at Google.
|
| |
|
|
| |
faux-InterlockedCompareExchange function was wrong: It works with LONG and not PVOID objects, and it needs to have the target marked as volatile. Further, it is not needed at all for x64 targets, since that platform always has the real McCoy.
|
| |
|
|
| |
conflicts with winbase.h on Windows.
|
| |
|
|
|
|
| |
2005 Team System.
Removed obsolete comment, since .dll modules are no longer supported on windows, only .pyd.
|
| | |
|
| |
|
|
|
|
| |
Revert bogus asserts (added to the wrong place) from rev 52501.
Approved by Anthony.
|
| |
|
|
| |
signed chars in frameobject.c which can occur with opcodes > 127
|
| |
|
|
|
| |
masked by a generic one with the message "unpack non-sequence".
(backport from rev. 54480)
|
| |
|
|
|
|
| |
complex if statements.
Backported from r54404.
|
| | |
|
| |
|
|
|
|
| |
Fixed by patch #922167.
Backported from r54291.
|
| |
|
|
| |
(backport)
|
| |
|
|
|
| |
sq_ass_slice instead of the sq_slice slot.
(backport from rev. 54139)
|
| | |
|
| |
|
|
| |
__del__).
|
| |
|
|
| |
unicode filenames
|
| |
|
|
| |
frame's thread state. Fixes #1579370.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
SF patch #1630975: Fix crash when replacing sys.stdout in sitecustomize
When running the interpreter in an environment that would cause it to set
stdout/stderr/stdin's encoding, having a sitecustomize that would replace
them with something other than PyFile objects would crash the interpreter.
Fix it by simply ignoring the encoding-setting for non-files.
This could do with a test, but I can think of no maintainable and portable
way to test this bug, short of adding a sitecustomize.py to the buildsystem
and have it always run with it (hmmm....)
|
| | |
|
| |
|
|
|
|
| |
Prevent crash on shutdown which can occur if we are finalizing
and the module dict has been cleared already and some object
raises a warning (like in a __del__).
|
| | |
|
