| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
and the .seed() and .whseed() methods failed to reset it. In other
words, setting the seed didn't completely determine the sequence of
results produced by random.gauss(). It does now. Programs repeatedly
mixing calls to a seed method with calls to gauss() may see different
results now.
Bugfix candidate (random.gauss() has always been broken in this way),
despite that it may change results.
|
|
|
|
|
| |
"What's New in Python 2.2" documented that these would be removed in
Python 2.3.
|
|
|
|
| |
See SF bug #551285.
|
|
|
|
| |
to make avoid regression.
|
|
|
|
| |
selections (eg "-u network") being ignored.
|
|
|
|
|
|
|
| |
and allocate it in one gulp.
This isn't a bugfix, it's just a minor optimization that may or may not
pay off.
|
|
|
|
|
| |
enumerate("abc") is an iterator returning (0,"a"), (1,"b"), (2,"c").
The argument can be an arbitrary iterable object.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
On Win2K it thought 'foo' started at byte offset 0 instead of at the
pagesize, and on Win98 it thought 'foo' didn't exist at all. Somehow
or other this is related to the new "in memory file" gimmicks in
bsddb, but the old bsddb we use on Windows sucks so bad anyway I don't
want to bother digging deeper. Flushing the file in test_mmap after
writing to it makes the problem go away, so good enough.
|
|
|
|
|
|
| |
build's "undetected error" problems were originally detected with
extension types, but we can whitebox test the same situations with
new-style classes.
|
|
|
|
|
| |
run_suite() instead of run_unittest(). Best practice is to plan for
multiple test classes.
|
|
|
|
|
|
| |
Also add a test that Python doesn't die with SIGXFSZ if it exceeds the
file rlimit. (Assuming this will also test the behavior when the 2GB
limit is exceed on a platform that doesn't have large file support.)
|
| |
|
|
|
|
| |
SF patch 545486
|
|
|
|
|
|
|
|
|
|
|
|
| |
closes SF #514433
can now pass 'None' as the filename for the bsddb.*open functions,
and you'll get an in-memory temporary store.
docs are ripped out of the bsddb dbopen man page. Fred may want to
clean them up.
Considering this for 2.2, but not 2.1.
|
|
|
|
|
|
|
|
|
| |
http://www.python.org/sf/444708
This adds the optional argument for str.strip
to unicode.strip too and makes it possible
to call str.strip with a unicode argument
and unicode.strip with a str argument.
|
| |
|
|
|
|
|
|
| |
test data: this test fails on WIndows now if universal newlines are
enabled (which they aren't yet, by default). I don't know whether the
test will also fail on Linux now.
|
|
|
|
| |
Related to SF bug #505315
|
|
|
|
|
|
| |
Bug fix by mhammond.
Bug fix candidate for 2.2, not present in 2.1.
|
|
|
|
|
| |
Use try/finally to ensure all Queue locks remain stable.
Includes test case. Bugfix candidate.
|
|
|
|
|
|
|
|
| |
a str subclass.
test_descr.py/string_exceptions(): New sub-test.
For 2.3 only. Guido doesn't want this backported.
|
|
|
|
|
|
|
|
| |
Close a file before trying to unlink it, and apparently Cygwin needs
writes to an mmap'ed file to get flushed before they're visible.
Bugfix candidate, but I think only for the 2.2 line (it's testing
features that I think were new in 2.2).
|
|
|
|
|
|
|
|
|
|
|
| |
Change type_get_doc (the get function for __doc__) to look in tp_dict
more often, and if it finds a descriptor in tp_dict, to call it (with
a NULL instance). This means you can add a __doc__ descriptor to a
new-style class that returns instance docs when called on an instance,
and class docs when called on a class -- or the same docs in either
case, but lazily computed.
I'll also check this into the 2.2 maintenance branch.
|
|
|
|
|
|
|
|
|
| |
If a str or unicode method returns the original object,
make sure that for str and unicode subclasses the original
will not be returned.
This should prevent SF bug http://www.python.org/sf/460020
from reappearing.
|
|
|
|
|
|
|
|
|
| |
PyNumber_InPlaceMultiply insisted on calling sq_inplace_repeat if it
existed, even if nb_inplace_multiply also existed and the arguments
weren't right for sq_inplace_repeat. Change this to only use
sq_inplace_repeat if nb_inplace_multiply isn't defined.
Bugfix candidate.
|
|
|
|
|
|
| |
(or platform independent). Closes SF bug #460357.
Bug fix candidate.
|
|
|
|
| |
intended whitespace.
|
|
|
|
| |
have the needed optional Japanese codecs installed.
|
|
|
|
|
| |
tab characters, so reverting the whitespace normalization. Barry,
please repair this.
|
| |
|
| |
|
|
|
|
| |
order in which the tests are normally run.
|
| |
|
|
|
|
| |
to keep doing that in every test that wants to filter a warning.
|
|
|
|
|
| |
because it *is* skipped. I'm not entirely sure it should be skipped, but
figuring that out would take actual thought <wink>.
|
|
|
|
| |
resetwarnings() calls too.
|
|
|
|
|
| |
regrtest framework. Keep the original standalone-unittest
scaffolding (i.e. suite() and __main__).
|
|
|
|
|
|
|
|
|
|
| |
Add a method zfill to str, unicode and UserString and change
Lib/string.py accordingly.
This activates the zfill version in unicodeobject.c that was
commented out and implements the same in stringobject.c. It also
adds the test for unicode support in Lib/string.py back in and
uses repr() instead() of str() (as it was before Lib/string.py 1.62)
|
|
|
|
|
|
|
| |
A stupid bug in object_set_class(): didn't check for value==NULL
before checking its type.
Bugfix candidate.
|
|
|
|
|
|
|
| |
complex_subtype_from_string(): this stopped parsing at the first 0
byte, as if that were the end of the input string.
Bugfix candidate.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add optional arg to string methods strip(), lstrip(), rstrip().
The optional arg specifies characters to delete.
Also for UserString.
Still to do:
- Misc/NEWS
- LaTeX docs (I did the docstrings though)
- Unicode methods, and Unicode support in the string methods.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The test function's signature should be
test(methodname, input, output, *args)
but the output argument was omitted. This caused all tests to fail,
because the expected output was passed as the initial argument to the
method call. But because of the way the test works (it compares the
results for a regular string to the results for a UserString instance
with the same value, and it's OK if both raise the same exception) the
test never failed!
I've fixed this, and also cleaned up a few warts in the verbose
output. Finally, I've made it possible to run the test stand-alone in
verbose mode by passing -v as a command line argument.
Now, the test will report failure related to zfill. That's not my
fault, that's a legitimate problem: the string_tests.py file contains
a test for the zfill() method (just added) but this method is not
implemented. The responsible party will surely fix this soon now.
|
| |
|
| |
|
|
|
|
| |
module necessarily raises.
|
| |
|