| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
|
|
|
|
|
| |
fixed.
(Jeremy, how did you discover that?)
|
| |
|
|
|
|
|
| |
an out-of-memory condition (and a hang on OSX). Filed a bug report
(#571845) to make sure this is eventually fixed.
|
| |
|
|
|
|
|
| |
running this as part of the regular test suite again, until I have
time to figure out why.
|
|
|
|
|
|
|
|
|
| |
http://mail.python.org/pipermail/python-dev/2002-June/025461.html
with test cases.
Also includes extended slice support for arrays, which I thought I'd
already checked in but obviously not.
|
|
|
|
|
| |
This is his SF patch 569697. I renamed main() to test_main() again so
that this is run as part of the standard test suite.
|
|
|
|
|
|
| |
In a fresh interpreter, type.mro(tuple) would segfault, because
PyType_Ready() isn't called for tuple yet. To fix, call
PyType_Ready(type) if type->tp_dict is NULL.
|
|
|
|
| |
time-zone independant
|
|
|
|
|
| |
trying to delete a .pyc file that didn't exist (it needed to delete .pyo
then).
|
|
|
|
| |
reason <wink>: can't unlink an open file on Windows.
|
| |
|
|
|
|
|
| |
Write 4 bytes for co_stacksize, etc. to prevent writing out
bad .pyc files which can cause a crash when read back in.
|
|
|
|
| |
Handle negative indices similar to slices.
|
| |
|
| |
|
|
|
|
|
| |
suggested there, based upon a better analysis (__getattr__ is a red
herring). Will backport to 2.2.
|
|
|
|
|
|
| |
They still run as standalone scripts, but when used as part of the
regression test suite, they are effectively no-ops.
(This is done by renaming test_main to main.)
|
|
|
|
|
|
| |
473985. Through a subtle rearrangement of some members in the etype
struct (!), mapping methods are now preferred over sequence methods,
which is necessary to support str.__getitem__("hello", slice(4)) etc.
|
|
|
|
| |
DNS, and we can't assume that.
|
|
|
|
|
|
|
|
|
|
|
| |
that retries the connect() call in timeout mode so it can be shared
between connect() and connect_ex(), and needs only a single #ifdef.
The test for this was doing funky stuff I don't approve of,
so I removed it in favor of a simpler test. This allowed me
to implement a simpler, "purer" form of the timeout retry code.
Hopefully that's enough (if you want to be fancy, use non-blocking
mode and decode the errors yourself, like before).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- setblocking(0) and settimeout(0) are now equivalent, and ditto for
setblocking(1) and settimeout(None).
- Don't raise an exception from internal_select(); let the final call
report the error (this means you will get an EAGAIN error instead of
an ETIMEDOUT error -- I don't care).
- Move the select to inside the Py_{BEGIN,END}_ALLOW_THREADS brackets,
so other theads can run (this was a bug in the original code).
- Redid the retry logic in connect() and connect_ex() to avoid masking
errors. This probably doesn't work for Windows yet; I'll fix that
next. It may also fail on other platforms, depending on what
retrying a connect does; I need help with this.
- Get rid of the retry logic in accept(). I don't think it was needed
at all. But I may be wrong.
|
|
|
|
| |
Add a sleep (yuck!) to _testRecvFrom() so the server can set up first.
|
| |
|
|
|
|
| |
using "".join(). Fold a long line.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
nonzero value is OK. Also fixed the error message for this and for
testGetSockOpt().
|
|
|
|
| |
information on what went wrong.
|
| |
|
|
|
|
|
| |
settimeout(), test settimeout(None), and the interaction between
settimeout() and setblocking().
|
|
|
|
| |
Changed test_timeout.py to conform to the guidelines in Lib/test/README.
|
|
|
|
| |
of a new-style instance are detected by the garbage collector.
|
|
|
|
|
|
|
|
|
|
| |
This was a simple typo. Strange that the compiler didn't catch it!
Instead of WHY_CONTINUE, two tests used CONTINUE_LOOP, which isn't a
why_code at all, but an opcode; but even though 'why' is declared as
an enum, comparing it to an int is apparently not even worth a
warning -- not in gcc, and not in VC++. :-(
Will fix in 2.2 too.
|
|
|
|
| |
slicelength. Include his test case.
|
|
|
|
|
|
|
|
|
| |
[ 400998 ] experimental support for extended slicing on lists
somewhat spruced up and better tested than it was when I wrote it.
Includes docs & tests. The whatsnew section needs expanding, and arrays
should support extended slices -- later.
|
| |
|
|
|
|
|
|
|
| |
The WeakKeyDictionary constructor didn't work when a dict arg was
given. Fixed by moving a line. Also adding a unit test.
Bugfix candidate.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I've made considerable changes to Michael's code, specifically to use
the select() system call directly and to store the timeout as a C
double instead of a Python object; internally, -1.0 (or anything
negative) represents the None from the API.
I'm not 100% sure that all corner cases are covered correctly, so
please keep an eye on this. Next I'm going to try it Windows before
Tim complains.
No way is this a bugfix candidate. :-)
|
|
|
|
|
|
| |
Straightforward fix. Will backport to 2.2. If there's ever a new 2.1
release, this could be backported there too (since it's an issue with
anything that's got both a __reduce__ and a __setstate__).
|
|
|
|
|
| |
Made conversion failure error messages consistent between types.
Added related unittests.
|
| |
|
| |
|
|
|
|
|
| |
Also, added more regression tests to cover the new type and test its
conformity with range().
|
|
|
|
|
| |
Change default for get() back to None.
Will backport to 2.2.1.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
While I was at it, I added a tp_clear handler and changed the
tp_dealloc handler to use the clear_slots helper for the tp_clear
handler.
Also tightened the rules for slot names: they must now be proper
identifiers (ignoring the dirty little fact that <ctype.h> is locale
sensitive).
Also set mp->flags = READONLY for the __weakref__ pseudo-slot.
Most of this is a 2.2 bugfix candidate; I'll apply it there myself.
|