- 01 Mar, 2008 4 commits
-
-
Barry Warsaw authored
-
Fred Drake authored
-
Barry Warsaw authored
-
Barry Warsaw authored
-
- 29 Feb, 2008 11 commits
-
-
Gerhard Häring authored
-
Martin v. Löwis authored
-
Martin v. Löwis authored
-
Martin v. Löwis authored
-
Georg Brandl authored
-
Martin v. Löwis authored
-
Georg Brandl authored
-
Martin v. Löwis authored
-
Mark Dickinson authored
-
Raymond Hettinger authored
-
Mark Dickinson authored
-
- 28 Feb, 2008 14 commits
-
-
Raymond Hettinger authored
-
Raymond Hettinger authored
Have itertools.chain() consume its inputs lazily instead of building a tuple of iterators at the outset.
-
Martin v. Löwis authored
-
Christian Heimes authored
-
Martin v. Löwis authored
-
Martin v. Löwis authored
-
Raymond Hettinger authored
-
Jeffrey Yasskin authored
didn't create, in most cases. When there are max_children handlers running, it will still wait for any child process, not just handler processes.
-
Andrew M. Kuchling authored
-
Christian Heimes authored
-
Raymond Hettinger authored
-
Jeffrey Yasskin authored
new thread had started. At least on my MacBook Pro, that wound up sleeping for a full 10ms (probably 1 jiffy). By using an Event instead, we can be absolutely certain that the thread has started, and return more quickly (217us). Before: $ ./python.exe -m timeit -s 'from threading import Thread' 't = Thread(); t.start(); t.join()' 100 loops, best of 3: 10.3 msec per loop $ ./python.exe -m timeit -s 'from threading import Thread; t = Thread()' 't.isAlive()' 1000000 loops, best of 3: 0.47 usec per loop After: $ ./python.exe -m timeit -s 'from threading import Thread' 't = Thread(); t.start(); t.join()' 1000 loops, best of 3: 217 usec per loop $ ./python.exe -m timeit -s 'from threading import Thread; t = Thread()' 't.isAlive()' 1000000 loops, best of 3: 0.86 usec per loop To be fair, the 10ms isn't CPU time, and other threads including the spawned one get to run during it. There are also some slightly more complicated ways to get back the .4us in isAlive() if we want.
-
Jeffrey Yasskin authored
sure all tests run even if some fail.
-
Jeffrey Yasskin authored
which forbids constructing types that have it set. The effect is to speed ./python.exe -m timeit -s 'import abc' -s 'class Foo(object): __metaclass__ = abc.ABCMeta' 'Foo()' up from 2.5us to 0.201us. This fixes issue 1762.
-
- 27 Feb, 2008 3 commits
-
-
Raymond Hettinger authored
-
Raymond Hettinger authored
-
Raymond Hettinger authored
-
- 26 Feb, 2008 8 commits
-
-
Raymond Hettinger authored
-
Georg Brandl authored
-
Christian Heimes authored
My tests don't show the promised speed up of 10%. The code is as fast as the old code for simple cases and slightly faster for complex cases with several of args and kwargs. But the patch simplifies the code, too.
-
Neal Norwitz authored
like waiting for socket timeouts in test_smtplib :-).
-
Christian Heimes authored
-
Neal Norwitz authored
(This may fail on some slow platforms, but we can fix those cases which should be relatively isolated and easier to find now.) Move two test cases that didn't require a server to be started to a separate TestCase. These tests were taking 3 seconds which is what the timeout was set to.
-
Georg Brandl authored
-
Neal Norwitz authored
-