- 13 Sep, 2018 9 commits
-
-
Benjamin Peterson authored
-
Eric V. Smith authored
This function was not in any .h file and was not used by Python, so removing it is safe. https://bugs.python.org/issue34653
-
Gregory P. Smith authored
[bpo-34658](https://www.bugs.python.org/issue34658): Fix a rare interpreter unhandled exception state SystemError only seen when using subprocess with a preexec_fn while an after_parent handler has been registered with os.register_at_fork and the fork system call fails. https://bugs.python.org/issue34658
-
Carol Willing authored
-
Gregory P. Smith authored
This causes the tearDown code to only unimport the test modules specifically created as part of each test via the self.mkhier method rather than abusing test.support.modules_setup() and the scary test.support.modules_cleanup() code. https://bugs.python.org/issue34200
-
Benjamin Peterson authored
A fix for 883702ebb8bbfa749ef0040d1b58d6222bf589ee.
-
Benjamin Peterson authored
-
Carol Willing authored
-
Carol Willing authored
-
- 12 Sep, 2018 20 commits
-
-
Benjamin Peterson authored
-
Benjamin Peterson authored
-
Tony Flury authored
-
Benjamin Peterson authored
closes bpo-34650: Check if sched_getscheduler returns ENOSYS before declaring it supported. (GH-9228) musl doesn't support the scheduler API, but declares stubs that alway return ENOSYS.
-
Alexey Izbyshev authored
Reported by Svace static analyzer.
-
Andrew Svetlov authored
-
Benjamin Peterson authored
Returning EINTR from pthread semaphore or lock acquisition is an optional POSIX feature. musl does not provide this feature, so some threadsignal tests fail when Python is built against it. There's no good way to test for musl, so we skip if we're on Linux and not using glibc pthreads. Also, hedge in the threading documentation about when we can provide interrupts from lock acquisition.
-
Oren Milman authored
-
Benjamin Peterson authored
-
Ethan Furman authored
* raise exception if _missing_ returns None or invalid type
-
Andrew Svetlov authored
Store a weak reference to stream readerfor breaking strong references It breaks the strong reference loop between reader and protocol and allows to detect and close the socket if the stream is deleted (garbage collected)
-
Bumsik Kim authored
-
Raymond Hettinger authored
-
orlnub123 authored
* Fix enum members getting shadowed by parent attributes * Move Enum._convert to EnumMeta._convert_ * Deprecate _convert
-
Ethan Furman authored
Improve Enum docs. https://bugs.python.org/issue33437
-
Benjamin Peterson authored
-
Sergey Fedoseev authored
-
Cheryl Sabella authored
-
Benjamin Peterson authored
-
Yury Selivanov authored
-
- 11 Sep, 2018 11 commits
-
-
Victor Stinner authored
In distutils.command.install, replace "pliant children" (previously, it was "pliant slaves") with "helpers". <!-- issue-number: [bpo-34605](https://www.bugs.python.org/issue34605) --> https://bugs.python.org/issue34605 <!-- /issue-number -->
-
Benjamin Peterson authored
It is unused. <!-- Thanks for your contribution! Please read this comment in its entirety. It's quite important. # Pull Request title It should be in the following format: ``` bpo-NNNN: Summary of the changes made ``` Where: bpo-NNNN refers to the issue number in the https://bugs.python.org. Most PRs will require an issue number. Trivial changes, like fixing a typo, do not need an issue. # Backport Pull Request title If this is a backport PR (PR made against branches other than `master`), please ensure that the PR title is in the following format: ``` [X.Y] <title from the original PR> (GH-NNNN) ``` Where: [X.Y] is the branch name, e.g. [3.6]. GH-NNNN refers to the PR number from `master`. -->
-
Sergey Fedoseev authored
Address a C undefined behavior signed integer overflow issue in set object table resizing. Our -fwrapv compiler flag and practical reasons why sets are unlikely to get this large should mean this was never an issue but it was incorrect code that generates code analysis warnings. <!-- issue-number: [bpo-1621](https://www.bugs.python.org/issue1621) --> https://bugs.python.org/issue1621 <!-- /issue-number -->
-
Max Bélanger authored
-
Sergey Fedoseev authored
When handling \s, \d, or \w (and their inverse) escapes in bytes regexes this a small but measurable performance improvement. <!-- issue-number: [bpo-34636](https://www.bugs.python.org/issue34636) --> https://bugs.python.org/issue34636 <!-- /issue-number -->
-
Benjamin Peterson authored
Followup to 90fc8980. <!-- Thanks for your contribution! Please read this comment in its entirety. It's quite important. # Pull Request title It should be in the following format: ``` bpo-NNNN: Summary of the changes made ``` Where: bpo-NNNN refers to the issue number in the https://bugs.python.org. Most PRs will require an issue number. Trivial changes, like fixing a typo, do not need an issue. # Backport Pull Request title If this is a backport PR (PR made against branches other than `master`), please ensure that the PR title is in the following format: ``` [X.Y] <title from the original PR> (GH-NNNN) ``` Where: [X.Y] is the branch name, e.g. [3.6]. GH-NNNN refers to the PR number from `master`. -->
-
Victor Stinner authored
This reverts commit 886483e2.
-
Benjamin Peterson authored
GCC complains: Python/pylifecycle.c: In function ‘_Py_InitializeFromConfig’: Python/pylifecycle.c:900:13: warning: ‘interp’ may be used uninitialized in this function [-Wmaybe-uninitialized] err = _Py_InitializeMainInterpreter(interp, &main_config); ~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This seems spurious since &interp is passed to _Py_InitializeCore. Anyway, we can easily initialize to quiet the warning.
-
Tal Einat authored
-
guoci authored
closes bpo-31902: Fix the col_offset attribute for ast.Async* nodes to point to the "async" keyword. (GH-4175) Previously, col_offset points to the keyword after "async".
-
Danish Prakash authored
Python 3.x does not fall back to comparing object addresses when comparing two `dt` objects. <!-- issue-number: [bpo-34365](https://www.bugs.python.org/issue34365) --> https://bugs.python.org/issue34365 <!-- /issue-number -->
-