| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| |
|
|
|
| |
Fix for 1.33: urlsplit() should only add '//' if scheme != ''.
[SF bug 620705]
|
| |
|
|
|
| |
uses bash and so does my 10.2 system. "limit stacksize 2048" is the
right invocation for tcsh/csh.
|
| |
|
|
|
| |
uses bash and so does my 10.2 system. "limit stacksize 2048" is the
right invocation for tcsh/csh.
|
| | |
|
| |
|
|
|
| |
There's no limit command near as I can tell. Should be the bash
builtin ulimit command.
|
| | |
|
| |
|
|
|
| |
Barry may want to update the news item about email 2.4.3 with more
details.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
SF bug 585882. Will forward-port.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
SF # 539360, webbrowser.py and konqueror, by Andy McKay
Fix Konqueror so it can start when calling open().
The assert needed to be on the raw URL, not openURL 'url...'
|
| | |
|
| |
|
|
| |
Add checks for size overflow on list*n, list+list, tuple+tuple.
|
| |
|
|
|
|
| |
and divmod() function for complex numbers.
Closes SF Bug 621708: Unclear deprecation.
|
| |
|
|
|
|
|
|
|
| |
PyObject_Init[Var] is almost always called from the PyObject_NEW[_VAR]
macros. The 'op' argument is then the result from PyObject_MALLOC,
and that can of course be NULL. In that case, PyObject_Init[Var]
would raise a SystemError with "NULL object passed to
PyObject_Init[Var]". But there's nothing the caller of the macro can
do about this. So PyObject_Init[Var] should call just PyErr_NoMemory.
|
| |
|
|
|
|
| |
The MS resource compiler can't do arithmetic. Fixed it by hand. Note
that the new PCbuild\field3.py was added to help with this, and injects
another manual step into the Python Windows release process.
|
| |
|
|
|
|
| |
resource compiler can't do correct arithmetic. The 3rd 16-bit int
in the "binary file version" we produce on Windows has been nonsense
as a result. I'll fix that next.
|
| |
|
|
| |
'release22-maint'.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Fix a nasty endcase reported by Armin Rigo in SF bug 618623:
'%2147483647d' % -123 segfaults. This was because an integer overflow
in a comparison caused the string resize to be skipped. After fixing
the overflow, this could call _PyString_Resize() with a negative size,
so I (1) test for that and raise MemoryError instead; (2) also added a
test for negative newsize to _PyString_Resize(), raising SystemError
as for all bad arguments.
An identical bug existed in unicodeobject.c, of course.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In inherit_slots(), get rid of the COPYSLOT(tp_dictoffset). Copying
the offset from a non-dominant base makes no sense: either the
non-dominant base has a nonzero tp_dictoffset, and then we should have
already copied it from the dominant base (at the very end of
inherit_special()), or the non-dominant base has no tp_dictoffset and
for some reason type_new() decided not to add one. The tp_dictoffset
from a non-dominant base is likely to conflict with the instance
layout of the dominant base, so copying the tp_dictoffset from the
non-dominant base would be a really bad idea in that case. This bug
can only be triggered by multiple inheritance from an extension class
that doesn't set tp_dictoffset and a new-style user-level class that
does have one. There are no such extension classes in the
distribution, but there are 3rd party ones. (Zope3 now has one,
that's how I found this. :-)
I've asked a few heavy users of new-style classes, extension classes
and metaclasses (David Abrahams and Kevin Jacobs), and neither of them
found any problems in their test suite after applying this fix, so I
assume it's safe.
|
| |
|
|
|
|
|
|
|
|
|
| |
The string formatting code has a test to switch to Unicode when %s
sees a Unicode argument. Unfortunately this test was also executed
for %r, because %s and %r share almost all of their code. This meant
that, if u is a unicode object while repr(u) is an 8-bit string
containing ASCII characters, '%r' % u is a *unicode* string containing
only ASCII characters!
Fixed by executing the test only for %s.
|
| | |
|
| | |
|
| |
|
|
| |
MacPython 2.2.
|
| |
|
|
|
| |
Reorganized so the test is skipped if os.popen() doesn't exist (in stead of fail
ing).
|
| | |
|
| | |
|
| |
|
|
| |
Fixes #620791.
|
| |
|
|
|
|
|
|
|
| |
runtime_library_dirs (i.e. -R flags) when building the _socket.so
module. Whitelist only the platforms we know need the flags, which
are only sunos (aka Solaris) platforms at the moment. Tested on
RH7.3, OSX 10.2, and Solaris 8.
Forward port candidate for Python 2.3.
|
| |
|
|
| |
Adjusted some markup to make the descriptions more consistent.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
list(xrange(sys.maxint / 4))
test. Changed 4 to 2.
The belief is that this test intended to trigger a bit of code in
listobject.c's NRESIZE macro that's looking for arithmetic overflow. As
written, it doesn't achieve that, though, and leaves it up to the platform
realloc() as to whether it wants to allocate 2 gigabytes. Some platforms
say "sure!", although they don't appear to mean it, and disaster ensues.
Changing 4 to 2 (just barely) manages to trigger the arithmetic overflow
test instead, leaving the platform realloc() out of it.
|
| |
|
|
|
|
| |
arbitrary versions of Expat.
Not applicable to Python 2.3, which will incorporate an Expat that does not
need this crutch.
|
| |
|
|
| |
in method name
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
checkin since 2.2.2b1 was released.
|
