| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
longer get special treatment. The Py_NotImplemented type is here as well.
|
|
|
|
| |
now as well.
|
|
|
|
| |
now as well.
|
| |
|
|
|
|
|
| |
types no longer get special treatment from abstract.c so more number number
methods have to be implemented.
|
| |
|
|
|
|
| |
Added test for second one.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
codec to not apply Latin-1 mappings for keys which are not found
in the mapping dictionaries, but instead treat them as undefined
mappings.
The patch was originally written by Martin v. Loewis with some
additional (cosmetic) changes and an updated test script
by Marc-Andre Lemburg.
The standard codecs were recreated from the most current files
available at the Unicode.org site using the Tools/scripts/gencodec.py
tool.
This patch closes the bugs #116285 and #119960.
|
|
|
|
| |
fixes bug #126345.
|
|
|
|
| |
in one place.
|
|
|
|
|
| |
incorrect % characters; characters outside the printable range are
replaced with '?'
|
|
|
|
| |
using GNU libc's getline()
|
| |
|
|
|
|
| |
index at which an unknown %-escape was found
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
a prime size, which is in fact never true anymore ...).
|
| |
|
|
|
|
|
|
| |
Fix type of the self parameter to some string object methods.
This closes patch #102670.
|
|
|
|
| |
Improved version coming soon to a Source Forge near you!
|
| |
|
|
|
|
|
| |
Complete with docos and tests.
OKed by Guido.
|
| |
|
| |
|
| |
|
|
|
|
| |
Fixes a typo that caused "".join(u"this is a test") to dump core.
|
|
|
|
|
| |
hack for TELL64()... Sounds like there's something else going on
really. Does anybody have a clue I can buy?
|
|
|
|
|
|
|
| |
*really* closes bug #121965.
Added three attributes to the xrange object: start, stop, and step. These
are the same as for the slice objects.
|
|
|
|
|
|
| |
where ">=" should have been.
This closes bug #121965.
|
|
|
|
|
|
|
| |
ranges) -- but thanks to the 2.0 compression scheme, this doesn't add
a single byte to the resulting binaries (!)
Closes bug #117524
|
|
|
|
|
|
| |
Changes to error messages to increase consistency & clarity.
This (mostly) closes SourceForge patch #101839.
|
|
|
|
|
|
|
| |
for the bug reported in Bug #116174: "%% %s" % u"abc" failed due
to the way string formatting delegated work to the Unicode formatting
function.
|
|
|
|
|
|
|
| |
Fix large file support for BeOS.
This closes SourceForge patch #101773. Refer to the patch discussion for
information on possible alternate fixes.
|
|
|
|
|
|
|
|
|
|
| |
raise ValueError. Checked in the patch as far as it went, but also changed
all of ints, longs and floats to raise ZeroDivisionError instead when raising
0 to a negative number. This is what 754-inspired stds require, as the "true
result" is an infinity obtained from finite operands, i.e. it's a singularity.
Also changed float pow to not be so timid about using its square-and-multiply
algorithm. Note that what math.pow does is unrelated to what builtin pow
does, and will still vary by platform.
|
|
|
|
|
| |
support for the last_is_sticky flag. A few hard to find bugs may be
fixed by this patch since the old code was buggy.
|
|
|
|
|
|
| |
result-object-pointer that is passed in, when an exception occurs during
coercion. The pointer has to be explicitly initialized in the caller to avoid
putting trash on the Python stack.
|
|
|
|
|
|
| |
#define'd to an unreasonable value (several recent gcc systems have
misdefined it, causing bogus overflows in integer multiplication). Nuke
CHAR_BIT entirely.
|
| |
|
|
|
|
|
|
| |
after unicode_empty has been freed, otherwise it might not point to
the real start of the unicode_freelist. Final closure for SF bug
#110681, Jitterbug PR#398.
|
|
|
|
| |
list. Discovered by Barry, fix approved by MAL.
|
|
|
|
|
|
|
|
| |
Add definitions of INT_MAX and LONG_MAX to pyport.h.
Remove includes of limits.h and conditional definitions of INT_MAX
and LONG_MAX elsewhere.
This closes SourceForge patch #101659 and bug #115323.
|
| |
|
|
|
|
|
| |
- use unidb compression for the unicodectype module. smaller, faster,
and slightly more portable...
|
|
|
|
|
|
|
|
| |
- use unidb compression for the unicodectype module. smaller, faster,
and slightly more portable...
(note: this commit doesn't include the unicodectype.c file itself; I'm
still waiting for the reviewers...)
|
|
|
|
|
| |
fncs are allowed to raise SIGFPE (see the C std), but OK by me if
people using --with-fpectl want to pay for checking anyway.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I fixed the specific complaint but left the (many) large issues untouched.
See the (very long) bug report discussion for why:
http://sourceforge.net/bugs/?func=detailbug&group_id=5470&bug_id=110624
Note that while I left the interface to the undocumented public API function
PyFloat_FromString alone, its 2nd argument is useless. From a comment block
in the code:
RED_FLAG 22-Sep-2000 tim
PyFloat_FromString's pend argument is braindead. Prior to this RED_FLAG,
1. If v was a regular string, *pend was set to point to its terminating
null byte. That's useless (the caller can find that without any
help from this function!).
2. If v was a Unicode string, or an object convertible to a character
buffer, *pend was set to point into stack trash (the auto temp
vector holding the character buffer). That was downright dangerous.
Since we can't change the interface of a public API function, pend is
still supported but now *officially* useless: if pend is not NULL,
*pend is set to NULL.
|