| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
internal error reporting by moving message to IDLE console.
|
|
|
|
|
|
|
|
|
| |
message claiming they were IDLE internal errors (since 1.2a1).
2. Add Ronald Oussoren to CREDITS
M NEWS.txt
M PyShell.py
M CREDITS.txt
|
| |
|
| |
|
|
|
|
|
| |
value is obtained by invoking hash on the long int.
Fixes #1536021.
|
| |
|
| |
|
|
|
|
| |
must not.
|
| |
|
|
|
|
| |
platforms that don't support changing thread stack size.
|
| |
|
|
|
|
| |
sys.stdin is closed.
|
| |
|
|
|
|
|
| |
Passing float arguments to struct.pack when integers are expected
now triggers a DeprecationWarning.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
In the 2.5 development cycle, MAKE_CLOSURE as changed to take free
variables as a tuple rather than as individual items on the stack.
Closes patch #1534084.
|
|
|
|
|
| |
in the byte code and co_consts even if they were not used, ie
immediately popped off the stack.
|
|
|
|
|
|
|
|
|
|
|
|
| |
on each iteration. I'm not positive this is the best way to handle
this. I'm also not sure that there aren't other cases where
the lnotab is generated incorrectly. It would be great if people
that use pdb or tracing could test heavily.
Also:
* Remove dead/duplicated code that wasn't used/necessary
because we already handled the docstring prior to entering the loop.
* add some debugging code into the compiler (#if 0'd out).
|
|
|
|
| |
str(exception) raised an exception.
|
|
|
|
| |
for stream decoder, but final=True for the decode function.
|
| |
|
|
|
|
|
| |
a socket operation on a socket with a timeout, the exception will be
caught correctly. Previously, the exception was not caught.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
writing the crc to file on the "PPC64 Debian trunk" buildbot
when running test_tarfile.
This is again a case where the native zlib crc is an unsigned
32-bit int, but the Python wrapper implicitly casts it to
signed C long, so that "the sign bit looks different" on
different platforms.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
buildbot (& possibly other 64-bit boxes) during test_gzip.
The native zlib crc32 function returns an unsigned 32-bit integer,
which the Python wrapper implicitly casts to C long. Therefore the
same crc can "look negative" on a 32-bit box but "look positive" on
a 64-bit box. This patch papers over that platform difference when
writing the crc to file.
It may be better to change the Python wrapper, either to make
the result "look positive" on all platforms (which means it may
have to return a Python long at times on a 32-bit box), or to
keep the sign the same across boxes. But that would be a visible
change in what users see, while the current hack changes no
visible behavior (well, apart from stopping the struct deprecation
warning).
Note that the module-level write32() function is no longer used.
|
| |
|
|
|
|
| |
KeyboardInterrupt.
|
|
|
|
|
|
|
|
|
| |
Patch by Douglas Greiman.
The test_run_abort() testcase produces a core file on Unix systems,
even though the test is successful. This can be confusing or alarming
to someone who runs 'make test' and then finds that the Python
interpreter apparently crashed.
|
|
|
|
|
|
|
|
|
| |
warning on Windows.
Afraid I can't detect a pattern to when the pack formats decide
to use a signed or unsigned format code -- appears nearly
arbitrary to my eyes. So I left all the pack formats alone and
changed the special-case data values instead.
|
|
|
|
|
|
|
|
|
|
|
| |
warnings on Win32.
Also added an XXX about the line:
pos3 = self.fp.tell()
`pos3` is never referenced, and I have no idea what the code
intended to do instead.
|
| |
|
|
|
|
| |
and may need to be reverted if it causes problems.
|
| |
|
| |
|
|
|
|
| |
Fixes #1257728.
|
|
|
|
| |
no longer maintained separatedly.
|
|
|
|
| |
Fixes #1525866.
|
|
|
|
| |
Pass the char* and size around rather than PyObject's.
|
|
|
|
| |
Also fix a SystemError when trying to assign to yield expressions.
|
| |
|
| |
|
| |
|
|
|
|
| |
This prevents garbage about command not found being printed on Solaris.
|
|
|
|
|
|
|
| |
These problems may mask more important, real problems.
One or both methods are known to fail on: Solaris, OpenBSD, Debian, Ubuntu.
They pass on Windows and some Linux boxes.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
41667, 41668 - initial switch to xmlcore
47044 - mention of xmlcore in What's New
50687 - mention of xmlcore in the library reference
re-apply xmlcore changes to xml:
41674 - line ending changes (re-applied manually), directory props
41677 - add cElementTree wrapper
41678 - PSF licensing for etree
41812 - whitespace normalization
42724 - fix svn:eol-style settings
43681, 43682 - remove Python version-compatibility cruft from minidom
46773 - fix encoding of \r\n\t in attr values in saxutils
47269 - added XMLParser alias for cElementTree compatibility
additional tests were added in Lib/test/test_sax.py that failed with
the xmlcore changes; these relate to SF bugs #1511497, #1513611
|