| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |
|
|
|
|
| |
[ 617309 ] getframe hook (Psyco #1)
Forward port candidate.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
SF #558432: Prevent Annoying ' ' from readline (Holker Krekel).
readline in all python versions is configured
to append a 'space' character for a successful
completion. But for almost all python expressions
'space' is not wanted (see coding conventions PEP 8).
For example if you have a function 'longfunction'
and you type 'longf<TAB>' you get 'longfunction '
as a completion. note the unwanted space at the
end.
The patch fixes this behaviour by setting readline's
append_character to '\0' which means don't append
anything. This doesn't work with readline < 2.1
(AFAIK nowadays readline2.2 is in good use).
An alternative approach would be to make the
append_character
accessable from python so that modules like
the rlcompleter.py can set it to '\0'.
[Ed.: I think expecting readline >= 2.2 is fine. If a completer wants
another character they can append that to the keyword in the list.]
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Patch for the DEC Alpha under Linux, by Lee Busby.
|
| |
|
|
|
| |
issues with varying versions of Expat; this completes the previous fix
for this version. (Not relevant for the trunk.)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
revision 2.36 of binascii.c
Another stab at SF 576327: zipfile when sizeof(long) == 8
binascii_crc32(): The previous patch forced this to return the same
result across platforms. This patch deals with that, on a 64-bit box,
the *entry* value may have "unexpected" bits in the high four bytes.
Bugfix candidate.
--------
More whitespace cleanup related conflict removal... sigh.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
revision 2.35 of binascii.c
Fix for SF bug #576327: zipfile when sizeof(long) == 8
binascii_crc32(): Make this return a signed 4-byte result across
platforms. The other way to make this platform-independent would be to
make it return an unsigned unbounded int, but the evidence suggests
other code out there treats it like a signed 4-byte int (e.g., existing
code writing the result with struct.pack "l" format).
Bugfix candidate.
|
| |
|
|
|
|
| |
On Windows, call WSAGetLastError() to retrieve the error number.
Bugfix candidate, will backport to release22-maint myself.
|
| |
|
|
|
|
| |
XML_Parser, which happens to be a pointer type, not an XML_Parser*.
This generated warnings when compiled with Expat 1.95.5, which no
longer defines XML_Parser to be void*.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
revision 2.87 of cPickle.c
Do more robust test of whether global objects are accessible.
PyImport_ImportModule() is not guaranteed to return a module object.
When another type of object was returned, the PyModule_GetDict() call
return NULL and the subsequent GetItem() seg faulted.
Bug fix candidate.
----------
Once again, whitespace chances scuppered automatic backporting, so
I did this by hand. Review probably wise -- but I have run make test!
Also incorporates revision 2.88 which was just removing a now unused
declaration.
|
| |
|
|
| |
#544265, Remove warnings for passing const to free()
|
| |
|
|
|
|
|
|
| |
(Most of) SF patch 601369 (Christos Georgiou): obmalloc,structmodule:
64bit, big endian (issue 2 only).
This adds a bunch of memcpy calls via a temporary variable to avoid
alignment errors. That's needed for some platforms.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
Raise ValueError if user passes a size to mmap which is larger
than the file.
Also need Tim's fix in test_mmap.py, 1.22 which flushes the file
before mmap'ing it.
|
| |
|
|
|
|
|
|
|
|
|
| |
revision 2.234 of posixmodule.c
SF bug 563750 (Alex Martelli): posix_tmpfile():
The file returned by tmpfile() has mode w+b, so use that in the call
to PyFile_FromFile().
Bugfix candidate.
|
| |
|
|
|
| |
popen2() and popen3() created text-mode pipes even when binary mode
was asked for. This was specific to Windows.
|
| |
|
|
|
|
|
|
|
| |
base64.decodestring('') should return '' instead of raising an
exception. The bug fix for SF #430849 wasn't quite right. This
closes SF bug #595671. I'll backport this to Python 2.2.
One addition here is that there was no test of the base64 module in
Python 2.2 cvs yet, so I added that too.
|
| | |
|
| |
|
|
| |
the extension building phase.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Backported from the trunk.
|
| |
|
|
| |
Closes SF bug #577774.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
2.2.1 has another bug that prevents the regression (which isn't a
regression at all) from showing up. "The regression" is actually a
glitch in cyclic gc that's been there forever.
As the generation being collected is analyzed, objects that can't be
collected (because, e.g., we find they're externally referenced, or
are in an unreachable cycle but have a __del__ method) are moved out
of the list of candidates. A tricksy scheme uses negative values of
gc_refs to mark such objects as being moved. However, the exact
negative value set at the start may become "more negative" over time
for objects not in the generation being collected, and the scheme was
checking for an exact match on the negative value originally assigned.
As a result, objects in generations older than the one being collected
could get scanned too, and yanked back into a younger generation. Doing
so doesn't lead to an error, but doesn't do any good, and can burn an
unbounded amount of time doing useless work.
A test case is simple (thanks to Kevin Jacobs for finding it!):
x = []
for i in xrange(200000):
x.append((1,))
Without the patch, this ends up scanning all of x on every gen0 collection,
scans all of x twice on every gen1 collection, and x gets yanked back into
gen1 on every gen0 collection. With the patch, once x gets to gen2, it's
never scanned again until another gen2 collection, and stays in gen2.
Opened another bug about that 2.2.1 isn't actually tracking (at least)
iterators, generators, and bound method objects, due to using the 2.1
gc API internally in those places (which #defines itself out of existence
in 2.2.x).
|
| | |
|
| |
|
|
|
| |
Based on patch contributed by Sean Reifschneider.
Closes SF patch #570618.
|
| |
|
|
| |
Warning caused by using &func. & is not necessary.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
The tp_new implementation should initialize the errorhandler field,
otherwise this code could segfault:
from socket import socket
s = socket.__new__(socket)
s.recv(100)
|
| |
|
|
|
| |
and got confused by certain log files. Remove logreader_refill and the
associated logic and replace with fgetc.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
(some tweaking for different _PyObject_GC_Malloc() call in 2.2. checked,
still returns the same thing on failure...)
_PyObject_GC_New: Could call PyObject_INIT with a NULL 1st argument.
_PyObject_GC_NewVar: Could call PyObject_INIT_VAR likewise.
Bugfix candidate.
Original patch(es):
python/dist/src/Modules/gcmodule.c:2.40
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Fix SF #544995 (zlib crash on second flush call)
Bug fix by mhammond.
Bug fix candidate for 2.2, not present in 2.1.
|
| |
|
|
|
|
|
| |
revision 2.28 of _localemodule.c
Don't imply XPG4 constants from CODESET presence. Fixes #534153.
2.2.2 candiate.
|
| |
|
|
|
| |
WITH_CYCLE_GC. (Neil pointed this out before the weekend, and I fixed
it right away, but forgot to check it in.)
|
| |
|
|
|
|
|
|
|
|
| |
This is Neil's fix for SF bug 535905 (Evil Trashcan and GC interaction).
The fix makes it possible to call PyObject_GC_UnTrack() more than once
on the same object, and then move the PyObject_GC_UnTrack() call to
*before* the trashcan code is invoked.
BUGFIX CANDIDATE!
|
| |
|
|
|
|
|
|
|
|
| |
revision 1.211 of socketmodule.c
Due to interaction between the MSL C library and the GUSI I/O library I can get reads from sockets to work consistently either for unbuffered binary files or for buffered binary files, but not for both:-(
The workaround is to force socket.makefile() to disable buffering for binary files.
Fixes bug 534625. 2.2.1 candidate.
|
| |
|
|
|
|
| |
[ 530285 ] redefining SRE_CODE in Modules/sre.h
Another one for the trunk, later.
|
| |
|
|
| |
Remove mentioning of -U option in "python -h" output.
|
| |
|
|
|
|
|
|
|
| |
Fix for
[ #504284 ] Last build problems on AIX
I'm ignoring the suggestion that this should be an autoconf test in the
interests of having a fix today. Feel free to quibble.
|
| |
|
|
|
|
| |
revision 2.23 of pypcre.c
Include Python.h first. Fixes #530159.
|
| |
|
|
|
|
| |
revision 2.26 of _localemodule.c
Verify arguments for nl_langinfo. Fixes #528879.
|