| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
assume tp_iter and later fields exist. Use PyObject_GenericGetAttr
instead of providing our own tp_getattr hook.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This is already removed from Expat 1.95.4, so the problem will not
recur when we update.
|
|
|
|
| |
isdigit().
|
|
|
|
| |
initial/default value.
|
|
|
|
| |
defined. /Really/ closes SF # 580631.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The implementation now stores all the lines of the request in a buffer
and makes a single send() call when the request is finished,
specifically when endheaders() is called.
This appears to improve performance. The old code called send() for
each line. The sends are all short, so they caused bad interactions
with the Nagle algorithm and delayed acknowledgements. In simple
tests, the second packet was delayed by 100s of ms. The second send was
delayed by the Nagle algorithm, waiting for the ack. The delayed ack
strategy delays the ack in hopes of piggybacking it on a data packet,
but the server won't send any data until it receives the complete
request.
This change minimizes the problem that Nagle + delayed ack will cause
a problem, although a request large enough to be broken into two
packets will still suffer some delay. Luckily the MSS is large enough
to accomodate most single packets.
XXX Bug fix candidate?
|
|
|
|
|
|
|
|
| |
PyType_Ready() because the tp_iternext slot is set (fortunately,
because using the tp_iternext implementation for the the next()
implementation is buggy). Also changed the allocation order in
enum_next() so that the underlying iterator is only moved ahead when
we have successfully allocated the result tuple and index.
|
|
|
|
|
|
| |
PyType_Ready() because the tp_iternext slot is set. Also removed the
redundant (and expensive!) call to raise StopIteration from
rangeiter_next().
|
|
|
|
|
|
|
|
|
|
| |
di_dict field when the end of the list is reached. Also make the
error ("dictionary changed size during iteration") a sticky state.
Also remove the next() method -- one is supplied automatically by
PyType_Ready() because the tp_iternext slot is set. That's a good
thing, because the implementation given here was buggy (it never
raised StopIteration).
|
|
|
|
|
|
|
|
|
|
| |
object references (it_seq for seqiterobject, it_callable and
it_sentinel for calliterobject) when the end of the list is reached.
Also remove the next() methods -- one is supplied automatically by
PyType_Ready() because the tp_iternext slot is set. That's a good
thing, because the implementation given here was buggy (it never
raised StopIteration).
|
| |
|
|
|
|
|
|
|
|
|
| |
it_seq field when the end of the list is reached.
Also remove the next() method -- one is supplied automatically by
PyType_Ready() because the tp_iternext slot is set. That's a good
thing, because the implementation given here was buggy (it never
raised StopIteration).
|
|
|
|
|
|
| |
discussion in python-dev with subject "Termination of two-arg iter()").
Implementation will follow.
|
|
|
|
|
| |
Some persistent picklers (well, probably, the *only* persistent
pickler) would like to pickle some classes in a special way.
|
|
|
|
|
|
| |
If the object is an ExtensionClass, for example, the slot is not even
defined. So we must check that the type has the slot (implied by
HAVE_CLASS) before calling tp_init().
|
|
|
|
|
|
|
|
|
|
|
| |
existed at the time atexit first got imported. That's a bug, and this
fixes it.
Also reworked test_atexit.py to test for this too, and to stop using
an "expected output" file, and to test what actually happens at exit
instead of just simulating what it thinks atexit will do at exit.
Bugfix candidate, but it's messy so I'll backport to 2.2 myself.
|
|
|
|
|
| |
but which is in a comment or string. Closes SF bug # 572341 reported
by Adrian van den Dries.
|
| |
|
|
|
|
|
|
| |
up the compile command's history. Fix that by using compile-internal.
Fixes SF bug # 580631
|
|
|
|
| |
the right thing even if char is unsigned.
|
| |
|
|
|
|
| |
time.sleep() will now be interrupted on the main thread when Ctrl+C is pressed. Other threads are never interrupted.
|
|
|
|
|
|
| |
by ISO 3166 as country codes, but the are reserved by IANA
nonetheless. The commonly used uk ccTLD is part of this group, near
as I can tell.
|
|
|
|
|
|
|
|
|
|
| |
disaster too, so this change is here to stay. Beefed up the comments
and added some stats Andrew reported. Also a small change to the
macro body, to make it obvious how XXXROUNDUP(0) ends up returning 0.
See SF patch 578297 for context.
Not a bugfix candidate, as the functional changes here have already
been backported to the 2.2 line (this patch just improves clarity).
|
| |
|
|
|
|
| |
full-blown windows.h, so changed accordingly.
|
|
|
|
| |
start-up.
|
|
|
|
|
|
| |
nodes (in Parser/node.c) resolves the gross memory consumption
exhibited by the EMX runtime on OS/2, so the test should be exercised
on this platform.
|
|
|
|
|
|
| |
explicit comparison function case: use PyObject_Call instead of
PyEval_CallObject. Same thing in context, but gives a 2.4% overall
speedup when sorting a list of ints via list.sort(__builtin__.cmp).
|
|
|
|
| |
Don't pass CREATE_NEW_CONSOLE to CreateProcess(), meaning our child process is in the same "console group" and therefore interrupted by the same Ctrl+C that interrupts the parent.
|
|
|
|
| |
This gets us closer to consistent Ctrl+C behaviour on NT and Win9x. NT now reliably generates KeyboardInterrupt exceptions for NT when a file IO operation was aborted. Bugfix candidate
|
|
|
|
|
|
|
| |
MSDN sample programs use it, apparently in error. The correct name
is WIN32_LEAN_AND_MEAN. After switching to the correct name, in two
cases more was needed because the code actually relied on things that
disappear when WIN32_LEAN_AND_MEAN is defined.
|
|
|
|
|
| |
remove unused macros
use co alias instead of f->f_code in macros
|
|
|
|
| |
platforms.
|
|
|
|
|
| |
Just declare it static so that lame (BAD_STATIC_FORWARD) compilers
don't see a mismatch between the prototype and the function.
|
|
|
|
|
| |
Use \cfunction instead of \function in various places
Add contributor names
|
|
|
|
| |
Closes SF bug #579991.
|
| |
|
|
|
|
|
|
|
|
| |
The test of httplib makes it difficult to maintain httplib. There are
two many idioms that pyclbr doesn't seem to understand, and I don't
understand how to update these tests to make them work.
Also remove commented out test of urllib2.
|
| |
|