| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |\
| |
| |
| | |
Patch contributed by Vajrasky Kok. Addresses Issue #17324
|
| | |
| |
| |
| | |
Patch contributed by Vajrasky Kok. Addresses Issue #17324
|
| |\ \
| |/
| |
| |
| | |
if all necessary functions are already found in libuuid.
Patch by Evgeny Sologubov.
|
| | |
| |
| |
| |
| | |
if all necessary functions are already found in libuuid.
Patch by Evgeny Sologubov.
|
| | |\ |
|
| | | |
| | |
| | |
| | | |
- my previous removal and hg resolve mark had still left them and hooks did not catch it too!
|
| |\ \ \ |
|
| | |\ \ \
| | | |/
| | |/|
| | | |
| | | | |
Improve the docstring of random.shuffle. Inform users not to provide int arg.
Addresses issue #14927
|
| | | | |
| | | |
| | | |
| | | | |
Addresses issue #14927
|
| |\ \ \ \
| | |_|/
| |/| | |
|
| | | |/
| |/| |
|
| | |/
|/|
| |
| | |
Suggested by Wouter Bolsterlee.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Due to recent changes, a Thread doesn't know that it's over before
someone calls .join() or .is_alive(). That meant repr(Thread)
continued to include "started" (and not "stopped") before one of
those methods was called, even if hours passed since the thread
ended.
Repaired that.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Antoine Pitrou found a variation that worked for him on the
thread+fork tests, and added an important
self._is_stopped = True
to the after-fork code. I confess I don't know why things passed
before. But then mixing fork with threads is insane ;-)
|
| | |
| |
| |
| | |
Unixy buildbots were failing the thread + fork tests :-(
|
| | |
| |
| |
| | |
Documented some obscurities, and assert'ed ._stop()'s crucial precondition.
|
| |\ \ |
|
| | |\ \
| | |/ |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The fix for issue 18808 left us checking two things to be sure a Thread
was done: an Event (._stopped) and a mutex (._tstate_lock). Clumsy &
brittle. This patch removes the Event, leaving just a happy lock :-)
The bulk of the patch removes two excruciating tests, which were
verifying sanity of the internals of the ._stopped Event after a fork.
Thanks to Antoine Pitrou for verifying that's the only real value
these tests had.
One consequence of moving from an Event to a mutex: waiters (threads
calling Thread.join()) used to block each on their own unique mutex
(internal to the ._stopped event), but now all contend on the same
mutex (._tstate_lock). These approaches have different performance
characteristics on different platforms. I don't think it matters in
this context.
|
| | |\ \
| | |/ |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
module is present (to record skipped tests)
|
| | | |
| | |
| | |
| | |
| | |
| | | |
already-stopped threads.
(AFAICT, in theory, we must reset all the locks, not just those in use)
|
| | |\ \ |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
faulthandler module if the variable is non-empty. Same behaviour than other
variables like PYTHONDONTWRITEBYTECODE.
|
| | | | | |
|
| | |/ /
| | |
| | |
| | | |
'--timeout' option requires faulthandler.dump_traceback_later).
|
| | | |
| | |
| | |
| | | |
default RLIMIT_NOFILE hard limit can be RLIMIT_INFINITY.
|
| | | |
| | |
| | |
| | | |
to avoid one extra FD per Connection.
|
| | |\ \
| | |/
| | |
| | |
| | | |
Fix the dead link of IEEE_854-1987 standard with the Wikipedia entry.
Addresses issue #18438
|
| | | |
| | |
| | |
| | | |
Addresses issue #18438
|
| | |\ \
| | |/ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When test.support was converted to a package, it started silently
skipping the tests which needed to download support data to run.
This change refactors the affected code, and also tidies up
test.support.findfile to remove the unused *here* parameter, document
the *subdir* parameter and rename the *filename* parameter to avoid
shadowing the file builtin and be consistent with the documentation.
The unexpected skips were noticed and reported by Zachary Ware
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
test_is_alive_after_fork is failing on some old Linux kernels, but
passing on all newer ones. Since virtually anything can go wrong
with locks when mixing threads with fork, replace the most likely
cause with a redundant simple data member.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
destroyed before returning.
This prevents unpredictable aborts in Py_EndInterpreter() when some non-daemon threads are still running.
|
| | | | |
|
| | |\ \
| | |/
| | |
| | |
| | | |
Fix License URL display and add test to check for license url presence.
Fixes issue #18206 Patch contributed by Berker Peksag and py.user
|
| | | |
| | |
| | |
| | | |
Fixes issue #18206 Patch contributed by Berker Peksag and py.user
|
| | | | |
|
| |/ / |
|
| |\ \
| |/
| |
| |
| |
| |
| | |
Issue 18944: fix a 1-character typo in test_set.py.
The error caused test_inline_methods() to test much less than intended.
Caught (& fixed) by Armin Rigo.
|
| | |
| |
| |
| |
| | |
The error caused test_inline_methods() to test much less than intended.
Caught (& fixed) by Armin Rigo.
|
| | | |
|
| | |
| |
| |
| | |
want to check that Connection.poll() doesn't crash.
|
| | |
| |
| |
| |
| |
| | |
test.support.
Patch by Valerie Lambert.
|
| | |
| |
| |
| | |
Patch by Berker Peksag.
|