| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
Change _begin() back to begin().
Fix for SF bug 579107.
Fix for SF bug #432621: httplib: multiple Set-Cookie headers
Fix SF bug #575360
Handle HTTP/0.9 responses.
|
| |
|
|
|
| |
The 2.1 maintenance branch is now identical to the trunk through rev
1.54 of httplib.py.
|
| |
|
|
|
|
| |
This fixes parseaddr() for the following RFC 2822 valid field:
To: User J. Person <person@dom.ain>
|
| |
|
|
| |
(The issues were re-numbered, not lost.)
|
| |
|
|
| |
See SF bug #551285.
|
| | |
|
| |
|
|
| |
not include 'True'. test_queue passes again.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
frameobject.c: make sure free and cell vars make it into locals, which
makes eval work.
bltinmodule.c & ceval.c: make sure a code object with free variables
that is passed to exec or eval raises an exception.
Also duplicate the current trunk test suite in the 2.1 branch, except
for certain necessary changes: different warnings raised by 2.1, need
for __future__.
|
| |
|
|
| |
'release21-maint'.
|
| |
|
|
| |
'release21-maint'.
|
| |
|
|
|
| |
The purpose is to avoid regression on SF bug #529273.
This test is stronger than the one submitted with the bug report.
|
| |
|
|
|
|
|
| |
Fix the second reincarnation of SF #456395 -- failure on IRIX. This
time use .replace() to change all \r\n into \n, not just the last one.
This makes test_pty work on Irix.
|
| |
|
|
| |
needed this anyway.
|
| |
|
|
| |
call test_main() at the end.
|
| |
|
|
| |
'release21-maint'.
|
| |
|
|
|
| |
Should raise TestSkipped, not ImportError, when deciding to skip the
test.
|
| |
|
|
|
|
|
|
|
|
| |
necessary in the 2.1 branch.) Guido's original checkin message:
A test suite for SocketServer.py that exposes the various bugs just
fixed. Regrettably, this must be run manually -- somehow the I/O
redirection of the regression test breaks the test. When run under
the regression test, this raises ImportError with a warning to that
effect.
|
| |
|
|
| |
'release21-maint'.
|
| |
|
|
|
|
|
| |
name when filling in the internal data structures, otherwise we incorrectly
raise a KeyError.
This fixes SF bug #432369.
|
| |
|
|
|
|
|
|
|
| |
SF bug 434186: 0x80000000/2 != 0x80000000>>1
i_divmod: New and simpler algorithm. Old one returned gibberish on most
boxes when the numerator was -sys.maxint-1. Oddly enough, it worked in the
release (not debug) build on Windows, because the compiler optimized away
some tricky sign manipulations that were incorrect in this case.
Makes you wonder <wink> ...
|
| | |
|
| |
|
|
| |
chickens work best!) adapt test_mutants to the absense of 'key in dict'.
|
| |
|
|
| |
'release21-maint'.
|
| |
|
|
|
|
|
|
| |
stringobject.c (2.114, 2.115) and test_strop.py (1.11, 1.12). Fixes
'replace' behaviour on systems on which 'malloc(0)' returns NULL (together
with previous checkins) and re-synchs the string-operation code in
stringobject.c and stropmodule.c, with the exception of 'replace', which has
the old semantics in stropmodule but the new semantics in stringobjects.
|
| | |
|
| |
|
|
|
|
|
| |
test_scope:1.8):
SF patch 419176 from MvL; fixed bug 418977
Two errors in dict_to_map() helper used by PyFrame_LocalsToFast().
|
| |
|
|
| |
Fix for bug #417030: "print '%*s' fails for unicode string"
|
| |
|
|
|
|
|
|
|
|
| |
Fix 2.1 nested scopes crash reported by Evan Simpson
The new test case demonstrates the bug. Be more careful in
symtable_resolve_free() to add a var to cells or frees only if it
won't be added under some other rule.
XXX Add new assertion that will catch this bug.
|
| |
|
|
|
|
|
|
|
|
| |
Fix 2.1 nested scopes crash reported by Evan Simpson
The new test case demonstrates the bug. Be more careful in
symtable_resolve_free() to add a var to cells or frees only if it
won't be added under some other rule.
XXX Add new assertion that will catch this bug.
|
| |
|
|
| |
recently reported bug; also exposed some other bugs in the implementation.
|
| |
|
|
|
|
| |
than from module pickletester. Using the latter turned out to cause
the test to break when invoked as "import test.test_pickle" or "import
test.autotest".
|
| |
|
|
|
| |
set to 'en' there -- Windows does not understand the 'en_US' locale.
The test succeeds there.
|
| |
|
|
|
| |
needed on some platforms (e.g. Solaris 8) when the test is run twice
in quick succession.
|
| |
|
|
|
| |
failing later when Python is compiled without threading but a failing
'threading' module can be imported due to an earlier (caught) attempt.
|
| |
|
|
|
|
|
| |
device to use, skip this test instead of allowing an error to occur
when we attempt to play sound on the absent device.
Verified by Mark Favas.
|
| |
|
|
|
|
| |
references to an object before calling registered callbacks).
Change last uses of verify() to self.assert_().
|
| | |
|
| |
|
|
|
|
|
|
|
| |
now raises NameError instead of UnboundLocalError, because the var in
question is definitely not local. (This affects test_scope.py)
Also update the recent fix by Ping using get_func_name(). Replace
tests of get_func_name() return value with call to get_func_desc() to
match all the other uses.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
fixes bug #414940, and redoes the fix for #129417 in a different way.
It also fixes a number of other problems with locale-specific formatting:
If there is leading or trailing spaces, then no grouping should be applied
in the spaces, and the total length of the string should not be changed
due to grouping.
Also added test case which works only if the en_US locale is available.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
"%#x" % 0
blew up, at heart because C sprintf supplies a base marker if and only if
the value is not 0. I then fixed that, by tolerating C's inconsistency
when it does %#x, and taking away that *Python* produced 0x0 when
formatting 0L (the "long" flavor of 0) under %#x itself. But after talking
with Guido, we agreed it would be better to supply 0x for the short int
case too, despite that it's inconsistent with C, because C is inconsistent
with itself and with Python's hex(0) (plus, while "%#x" % 0 didn't work
before, "%#x" % 0L *did*, and returned "0x0"). Similarly for %#X conversion.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
http://sourceforge.net/tracker/index.php?func=detail&aid=415514&group_id=5470&atid=105470
For short ints, Python defers to the platform C library to figure out what
%#x should do. The code asserted that the platform C returned a string
beginning with "0x". However, that's not true when-- and only when --the
*value* being formatted is 0. Changed the code to live with C's inconsistency
here. In the meantime, the problem does not arise if you format a long 0 (0L)
instead. However, that's because the code *we* wrote to do %#x conversions on
longs produces a leading "0x" regardless of value. That's probably wrong too:
we should drop leading "0x", for consistency with C, when (& only when) formatting
0L. So I changed the long formatting code to do that too.
|
| |
|
|
|
| |
platform. If it returns pi on the unixware7 platform, they have a bug in
their libm atan2.
|
| | |
|
| |
|
|
| |
Fix to SF bug #414743 based on Michael Hudson's patch #414750.
|
| |
|
|
| |
instead of using the mapping() function.
|