| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
| |
contains
info for all processed zip files, even when they are no longer used.
|
| | |
|
| |
|
|
|
|
| |
math.pow behave on alpha Tru64. All IEEE 754
special values are now handled directly; only
the finite**finite case is handled by libm.
|
| |
|
|
|
| |
test_math, to help track down debian-alpha
buildbot failure.
|
| |
|
|
|
| |
handling code in math.pow, in the hope of making all
tests pass on the alpha Tru64 buildbot.
|
| |
|
|
| |
The bits and pieces for the Windows side were already in place. The POSIX side is trivial (as usual) and uses os.kill().
|
| |
|
|
| |
Perform additional cleanup, mostly deleting from sys.modules, or clearing the warnings registry.
|
| |
|
|
|
|
| |
The patch is collaborated work of Mark Dickinson and me. It was mostly done a few months ago. The patch fixes a lot of loose ends and edge cases related to operations with NaN, INF, very small values and complex math.
The patch also adds acosh, asinh, atanh, log1p and copysign to all platforms. Finally it fixes differences between platforms like different results or exceptions for edge cases. Have fun :)
|
| | |
|
| | |
|
| |
|
|
| |
number of splits.
|
| |
|
|
| |
Windows.
|
| | |
|
| |
|
|
| |
when it is run.
|
| |
|
|
|
|
|
|
|
| |
'warnings' code in places where it was previously not possible (e.g., the
parser). It could also potentially lead to a speed-up in interpreter start-up
if the C version of the code (_warnings) is imported over the use of the
Python version in key places.
Closes issue #1631171.
|
| |
|
|
|
|
| |
This might help fix some of the failures on Windows box(es). It doesn't hurt
either way and ensure the tests are a little more self contained (ie have
less assumptions).
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
It tried to allocate negative or zero memory. That fails.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
to listen on in network-oriented tests has been refined in an effort to
facilitate running multiple instances of the entire regression test suite
in parallel without issue. test_support.bind_port() has been fixed such
that it will always return a unique port -- which wasn't always the case
with the previous implementation, especially if socket options had been
set that affected address reuse (i.e. SO_REUSEADDR, SO_REUSEPORT). The
new implementation of bind_port() will actually raise an exception if it
is passed an AF_INET/SOCK_STREAM socket with either the SO_REUSEADDR or
SO_REUSEPORT socket option set. Furthermore, if available, bind_port()
will set the SO_EXCLUSIVEADDRUSE option on the socket it's been passed.
This currently only applies to Windows. This option prevents any other
sockets from binding to the host/port we've bound to, thus removing the
possibility of the 'non-deterministic' behaviour, as Microsoft puts it,
that occurs when a second SOCK_STREAM socket binds and accepts to a
host/port that's already been bound by another socket. The optional
preferred port parameter to bind_port() has been removed. Under no
circumstances should tests be hard coding ports!
test_support.find_unused_port() has also been introduced, which will pass
a temporary socket object to bind_port() in order to obtain an unused port.
The temporary socket object is then closed and deleted, and the port is
returned. This method should only be used for obtaining an unused port
in order to pass to an external program (i.e. the -accept [port] argument
to openssl's s_server mode) or as a parameter to a server-oriented class
that doesn't give you direct access to the underlying socket used.
Finally, test_support.HOST has been introduced, which should be used for
the host argument of any relevant socket calls (i.e. bind and connect).
The following tests were updated to following the new conventions:
test_socket, test_smtplib, test_asyncore, test_ssl, test_httplib,
test_poplib, test_ftplib, test_telnetlib, test_socketserver,
test_asynchat and test_socket_ssl.
It is now possible for multiple instances of the regression test suite to
run in parallel without issue.
|
| |
|
|
|
|
|
| |
suite as a side-effect of importing the module.
- in test_capi, a thread tried to import other modules
- re.compile() imported sre_parse again on every call.
|
| |
|
|
|
|
|
|
|
|
|
| |
close() will now raise an IOError if any operations on the file object
are currently in progress in other threads.
Most code was written by Antoine Pitrou (pitrou). Additional testing,
documentation and test suite cleanup done by me (gregory.p.smith).
Fixes issue 815646 and 595601 (as well as many other bugs and
references to this problem dating back to the dawn of Python).
|
| |
|
|
|
|
|
|
| |
HandlerBException is ignored, and fix one such problem, where it was thrown
during the __del__ method of the previous Popen object.
We may want to find a better way of printing verbose information so it's not
spammy when the test passes.
|
| |
|
|
| |
buildbots was certainly useful. All of the platforms that have some form of BSD lineage -- FreeBSD, OS X, Solaris and Tru64 -- all pass the test. Windows and Linux, on the other hand, don't. Windows I knew about, Linux was a surprise. Knowing this, I believe a more appropriate fix will revolve around test_support.bind_socket() -- this method needs to return a port that nothing in the system has bound already. The best way to do this may just be to rely on ephemeral ports, rather than having the user specify a desired port, then fall back to four random ports, then try 0.
|
| |
|
|
| |
is called on identical (host, port) combinations in two separate sockets. This should raise an EADDRINUSE socket.error in all cases, irrespective of whether or not SO_REUSEADDR is set on the sockets. However, with Windows, when SO_REUSEADDR is set on the sockets, no error is thrown (an error is thrown when the option isn't set), which results in an extremely wedged python process whenever accept() is called on either of the bound sockets. I'm committing this test now to observe if it's only Windows that has this behaviour (via the buildbots). Note: this WILL break all Windows buildbots for now; once I've observed the results on other platforms, I'll revert, then start looking into a patch.
|
| | |
|
| |
|
|
|
| |
And fix some flakiness in test_itimer_prof, which could detect that the timer
had reached 0 before the signal arrived announcing that fact.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
sys.settrace
calls threading.currentThread.
The correction somewhat improves the code, but it was close.
Many thanks to the "with" construct, which turns python code into C calls.
I wonder if it is not better to sys.settrace(None) just after
running the __main__ module and before finalization.
|
| | |
|
| |
|
|
| |
on various platforms, most recently the Alpha Tru64.
|
| |
|
|
| |
test_itimer_prof.
|
| |
|
|
|
|
| |
after the first run.
Rebuild the DocTestSuite on each iteration.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When cls is an ABCMeta, every call to isinstance(x, cls)
records type(x) in the cls._abc_cache of cls_abc_negative_cache.
So we clear these caches at the end of the test.
inspect.isabstract() is not the correct test for all ABCs, because there is no @abstractmethod in io.py (why?)
isinstance(cls, ABCMeta) would be more exact, but it fails with an infinite recursion.
So I used a hack to determine whether a class is an ABCMeta.
The true correction would be to turn cls._abc_cache &co into a WeakSet, as py3k does.
But classic classes are not weak referenceable...
Of course, this change should not be merged into the py3k branch.
|
| |
|
|
|
| |
it registers the same codec on each iteration.
Do it only once at load time.
|
| |
|
|
|
|
| |
with python 2.6, enumerating bytes yields 1-char strings, not numbers.
Don't merge this into the py3k branch.
|
| |
|
|
| |
of effort to do so.
|
| |
|
|
| |
it is easy to capture stderr if desired.
|
| |
|
|
|
| |
fine, but the last change may be required for the test to pass on Windows.
Should we always close the mmap too?
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Thanks to Wummel for the patch
|
| |
|
|
| |
the test itself doesn't do anything on windows, focus on setUp and tearDown.
|
| |
|
|
|
|
| |
http://www.python.org/dev/buildbot/trunk/x86%20W2k8%20trunk/builds/255/step-test/0
Temporarily increase verbosity of this test.
|
| |
|
|
| |
compile() when compiling an AST node.
|
| |
|
|
|
| |
except in verbose mode.
Support code is much simpler.
|
| |
|
|
| |
otherwise running test_logging twice produce the errors we see on all buildbots
|
