| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* unified the way intobject, longobject and mystrtoul handle
values around -sys.maxint-1.
* in general, trying to entierely avoid overflows in any computation
involving signed ints or longs is extremely involved. Fixed a few
simple cases where a compiler might be too clever (but that's all
guesswork).
* more overflow checks against bad data in marshal.c.
* 2.5 specific: fixed a number of places that were still confusing int
and Py_ssize_t. Some of them could potentially have caused
"real-world" breakage.
* list.pop(x): fixing overflow issues on x was messy. I just reverted
to PyArg_ParseTuple("n"), which does the right thing. (An obscure
test was trying to give a Decimal to list.pop()... doesn't make
sense any more IMHO)
* trying to write a few tests...
|
|
|
|
|
| |
on undefined behaviour of the C compiler anymore.
Will backport to 2.5 and 2.4.
|
| |
|
|
|
|
| |
Will backport.
|
|
|
|
| |
string pointed to by its parameter.
|
|
|
|
| |
to encodings.search_function() contains a dot.
|
|
|
|
| |
datetime's strftime function.
|
|
|
|
| |
but also for functions.
|
|
|
|
| |
keep_blank_values and strict_parsing keyword arguments.
|
|
|
|
| |
with a slash.
|
| |
|
|
|
|
| |
number of arguments, as was the case in Python 2.4.
|
|
|
|
|
| |
keyword arguments any more (previously they accepted them, but didn't
use them).
|
|
|
|
| |
GNOME browser in case it is a command with args.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
being raised when print_exc() was called without an exception set.
In version 2.4, this printed "None", restored that behavior.
|
|
|
|
|
| |
not being recognized as a keyword after, e.g., this statement:
from __future__ import division, with_statement
|
| |
|
|
|
|
|
|
|
| |
These tests should be improved. Hopefully this fixes variations when
flipping back and forth between fpdef and fplist.
Backport candidate.
|
|
|
|
|
|
|
|
|
|
| |
In addition to testing positive numbers, verify negative numbers work in configure.
In order to avoid compiler warnings on OS X 10.4, also change the order of the check
for the format character to use (PY_FORMAT_SIZE_T) in the sprintf format
for Py_ssize_t. This patch changes PY_FORMAT_SIZE_T from "" to "l" if it wasn't
defined at configure time. Need to verify the buildbot results.
Backport candidate (if everyone thinks this patch can't be improved).
|
| |
|
| |
|
|
|
|
|
|
|
| |
(e.g., ``BaseException(1,2,3)[0:2]``).
Discovered in Python 2.5.0 by Thomas Heller and reported to python-dev. This
should be backported to 2.5 .
|
|
|
|
| |
from exceptions.
|
|
|
|
|
|
| |
arguments are transposed. (reported by Louis Zechtzer)
..already committed to release24-maint
..needs committing to release25-maint
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Building with HP's cc on HP-UX turned up a couple of problems.
_PyGILState_NoteThreadState was declared as static inconsistently.
Make it static as it's not necessary outside of this module.
Some tests failed because errno was reset to 0. (I think the tests
that failed were at least: test_fcntl and test_mailbox).
Ensure that errno doesn't change after a call to Py_END_ALLOW_THREADS.
This only affected debug builds.
|
|
|
|
|
|
|
| |
As mentioned on python-dev, reverting patch #1504333 because it introduced
an infinite loop in rev 47154.
This patch also adds a test to prevent the regression.
|
| |
|
| |
|
|
|
|
| |
offending buildbot
|
| |
|
| |
|
| |
|
|
|
|
| |
imports (if not in package and if beyond toplevel package).
|
|
|
|
| |
of os.urandom().
|
| |
|
|
|
|
| |
subprocess module.
|
| |
|
|
|
|
|
|
|
|
| |
- gbk and gb18030 codec now handle U+30FB KATAKANA MIDDLE DOT correctly.
- iso2022_jp_2 codec now encodes into G0 for KS X 1001, GB2312
codepoints to conform the standard.
- iso2022_jp_3 and iso2022_jp_2004 codec can encode JIS X 2013:2
codepoints now.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
generator expressions (x for x, in ... ) works again.
Sigh, I only fixed for loops the first time, not list comps and genexprs too.
I couldn't find any more unpacking cases where there is a similar bug lurking.
This code should be refactored to eliminate the duplication. I'm sure
the listcomp/genexpr code can be refactored. I'm not sure if the for loop
can re-use any of the same code though.
Will backport to 2.5 (the only place it matters).
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
i_divmod(): As discussed on Python-Dev, changed the overflow
checking to live happily with recent gcc optimizations that
assume signed integer arithmetic never overflows.
This differs from the corresponding change on the 2.5 and 2.4
branches, using a less obscure approach, but one that /may/
tickle platform idiocies in their definitions of LONG_MIN.
The 2.4 + 2.5 change avoided introducing a dependence on
LONG_MIN, at the cost of substantially goofier code.
|
| |
|