| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
week.
|
|
|
|
| |
should always have it.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
at random, and replaces the elements at those positions with new random
values. I was pleasantly surprised by how fast this goes! It's hard to
conceive of an algorithm that could special-case for this effectively.
Plus it's exactly what happens if a burst of gamma rays corrupts your
sorted database on disk <wink>.
i 2**i *sort ... %sort
15 32768 0.18 ... 0.03
16 65536 0.24 ... 0.04
17 131072 0.53 ... 0.08
18 262144 1.17 ... 0.16
19 524288 2.56 ... 0.35
20 1048576 5.54 ... 0.77
|
|
|
|
|
|
| |
and age of rampant computer breakins I imagine there are plenty of systems
with telnet disabled. Successful check of at least one getservbyname() call
is required for success
|
| |
|
|
|
|
|
|
|
|
| |
The __delete__ method wrapper for descriptors was not supported
(I added a test, too.)
2.2 bugfix candidate.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
in the stability tests.
Bizarre: this takes 11x longer to run if and only if test_longexp is
run before it, on my box. The bigger REPS is in test_longexp, the
slower this gets. What happens on your box? It's not gc on my box
(which is good, because gc isn't a plausible candidate here).
The slowdown is massive in the parts of test_sort that implicitly
invoke a new-style class's __lt__ or __cmp__ methods. If I boost
REPS large enough in test_longexp, even the test_sort tests on an array
of size 64 visibly c-r-a-w-l. The relative slowdown is even worse in
a debug build. And if I reduce REPS in test_longexp, the slowdown in
test_sort goes away.
test_longexp does do horrid things to Win98's management of user
address space, but I thought I had made that a whole lot better a month
or so ago (by overallocating aggressively in the parser).
|
|
|
|
| |
arguments correctly too.
|
|
|
|
|
|
| |
+ Don't change the arglist requirements.
+ Give the wrapper the same docstring as _socket.socket (it didn't
have any docstring).
|
|
|
|
| |
1.6, and pierslauder didn't respond to email about it on Monday.
|
|
|
|
|
| |
thinking that he was running his new test by running "make test".
Also, I can't get this to fail any more. Your turn. :-)
|
|
|
|
|
|
| |
If the long is large enough, the return value will be a negative int.
In this case, calling the function a second time won't return the
original value passed in.
|
|
|
|
|
|
|
|
| |
imports of test modules now import from the test package. Other
related oddities are also fixed (like DeprecationWarning filters that
weren't specifying the full import part, etc.). Also did a general
code cleanup to remove all "from test.test_support import *"'s. Other
from...import *'s weren't changed.
|
|
|
|
|
|
|
|
|
| |
See there for a description.
Added test case.
Bugfix candidate for 2.2.x, not sure about previous versions:
probably low priority, because virtually no one runs debug builds.
|
|
|
|
|
|
| |
[ 587875 ] crash on deleting extended slice
The array code got simpler, always a good thing!
|
|
|
|
| |
of encodings. Skip modules that don't have a getregentry function.
|
| |
|
|
|
|
| |
there.
|
| |
|
|
|
|
|
|
|
|
| |
'%g' % '1'
'%d' % '1'
Add a test for these conditions
Fix the test so that if not exception is raise, this is a failure
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
to executing Run/F5 from an EditorWindow.
M ScriptBinding.py : add call to clear_the_environment()
M run.py : implemented Executive.clear_the_environment()
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
failing).
|
|
|
|
|
|
|
| |
Idle client and localhost origin of connection is verified by client.
M PyShell.py
M rpc.py
M run.py
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Fixes SF bug #568322.
The code should raise an OverflowError if the long is > 32 bits, even
on platforms where sizeof(long) > 4.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
imports e.g. test_support must do so using an absolute package name
such as "import test.test_support" or "from test import test_support".
This also updates the README in Lib/test, and gets rid of the
duplicate data dirctory in Lib/test/data (replaced by
Lib/email/test/data).
Now Tim and Jack can have at it. :)
|
|
|
|
| |
character set, which we'll convert to a Charset instance. Sigh.
|
|
|
|
| |
will return as the charset if implicit us-ascii is used.
|
|
|
|
| |
Return the selected item, if there is any.
|
|
|
|
|
|
|
|
|
|
| |
array. Our samplesort special-cases the snot out of this, running about
12x faster than *sort. The experimental mergesort runs it about 8x
faster than *sort without special-casing, but should really do better
than that (when merging runs of different lengths, right now it only
does something clever about finding where the second run begins in
the first and where the first run ends in the second, and that's more
of a temp-memory optimization).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
from test.test_support import TestSkipped, run_unittest
to
from test_support import TestSkipped, run_unittest
Otherwise, if the Japanese codecs aren't installed, regrtest doesn't
believe the TestSkipped exception raised by this test matches the
except (ImportError, test_support.TestSkipped), msg:
it's looking for, and reports the skip as a crash failure instead of
as a skipped test.
I suppose this will make it harder to run this test outside of
regrtest, but under the assumption only Barry does that, better to
make it skip cleanly for everyone else.
|
|
|
|
| |
opened on top of the shell instead of in a new window.
|
| |
|
|
|
|
| |
It's a little better than average for our sort.
|
|
|
|
| |
'en' in teardown(). This way hopefully test_time.py won't fail.
|