| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
| |
|
| |
|
|
|
| |
Mitigate performance regression of the list comparison caused by 2d5bf56.
|
|
|
|
|
|
| |
PyObject_RichCompareBool (GH-17734)
Take strong references before calling PyObject_RichCompareBool to protect against the case
where the object dies during the call.
|
|
|
|
| |
Tag memoryview, range, and tuple as classes, the same as list, etcetera, in
the library manual built-in functions list.
|
|
|
| |
Hold strong references to list elements while calling PyObject_RichCompareBool().
|
|
|
|
|
|
| |
(GH-17560)
|
| |
|
|
|
|
| |
(GH-16977)
|
| |
|
|
|
|
|
|
|
|
|
|
| |
(GH-17608)
* __enter__ is now looked up before __exit__ to give a more intuitive error message
* add pseudo-code equivalent for the with statement
* fix pseudo-code for the async with statement to use a finally clause
* use SUITE rather than BLOCK for consistency with the language grammar
Patch by Géry Ogam.
|
| |
|
|
|
|
| |
privileges to use pidfd (GH-17740)
|
| |
|
|
|
|
| |
test_unparse (GH-17738)
|
|
|
|
|
|
|
| |
The importlib.metadata documentation uses hardcoded links to internal
pages. This results in minor rendering issues. This change replaces
the hardcoded links with suitable Sphinx roles.
Signed-off-by: Oleg Höfling <oleg.hoefling@gmail.com>
|
|
|
|
|
| |
funtion -> function; configuraton -> configuration; defintitions -> definitions;
focusses -> focuses; necesarily -> necessarily; follwing -> following;
Excape -> Escape,
|
| |
|
|
|
|
| |
Python stdlib files (GH-17721)
|
|
|
|
|
|
| |
The comment about the collection rules for the permanent generation was
incorrectly referenced by a comment in gcmodule.c (the comment has been
moved long ago into a header file). Moving the comment into the relevant
code helps with readability and avoids broken references.
|
|
|
|
|
| |
`time.clock()` was removed in Python 3.8, but it was still mentioned
in the documentation for when `time.get_clock_info()` is given the
argument `'clock'`. This commit removes that mention.
|
|
|
|
| |
(GH-17702)
|
| |
|
|
|
|
|
| |
Fixed small grammatical issue
Automerge-Triggered-By: @Mariatta
|
|
|
|
| |
(GH-17677)
|
|
|
| |
A character "i" is omitted.
|
|
|
|
|
|
|
|
| |
Small typo/formatting corrections.
`whethen` -> `whether`
`exaustion' -> `exhaustion`
Assorted appending periods `.` and slight reformattings to place `Path contributed by` on the same line as description, matching the majority of document.
NB Some of these might need to be backported, as I saw the first error in the [changelog for 3.8.1](https://docs.python.org/3.8/whatsnew/changelog.html#python-3-8-1)
|
|
|
|
|
|
|
| |
The added parentheses around the PyIter_Next assignment suppress the following warning which gcc throws without:
```
warning: using the result of an assignment as a condition without parentheses [-Wparentheses]
```
The other change is a typo fix
|
| |
|
| |
|
|
|
|
|
| |
regression on import (GH-17376)" (GH-17687)
This reverts commit ded8888fbc33011dd39b7b1c86a5adfacc4943f3.
|
|
|
|
|
| |
Co-Authored-By: Victor Stinner <vstinner@python.org>
Co-authored-by: Pablo Galindo <pablogsal@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When checking `setup.py` and when the `author` field was provided, but
the `author_email` field was missing, erroneously a warning message was
displayed that the `author_email` field is required.
The specs do not require the `author_email`field:
https://packaging.python.org/specifications/core-metadata/#author
The same is valid for `maintainer` and `maintainer_email`.
The warning message has been adjusted.
modified: Doc/distutils/examples.rst
modified: Lib/distutils/command/check.py
https://bugs.python.org/issue38914
|
|
|
|
|
|
|
|
|
| |
Fixes a nearly word for word duplication of a sentence that appears
earlier in the caution section of datetime.datetime.fromisoformat in
Doc/Library/datetime.rst.
No issue created as it's a trivial change.
Automerge-Triggered-By: @pganssle
|
|
|
| |
"HH", "MM" and "ffffff" are enclosed with double back quotes, but "SS" is left being bare
|
|
|
|
| |
Quick subclasshook fix using the same method is being used in collections.abc (up to a certain degree).
|
|
|
|
|
|
|
|
|
|
|
| |
table (GH-17408)
Adds` __module__ ` entries for function & method types in inspect docs table.
https://bugs.python.org/issue38918
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Fix test_ressources_gced_in_workers() of test_concurrent_futures:
explicitly stop the manager to prevent leaking a child process
running in the background after the test completes.
|
|
|
|
|
|
|
|
| |
All keywords should first be checked for pointer identity. Only
after that failed for all keywords (unlikely) should unicode
equality be used.
The original code would call unicode equality on any non-matching
keyword argument. Meaning calling it often e.g. when a function
has many kwargs but only the last one is provided.
|
|
|
|
| |
Co-Authored-By: Pablo Galindo <Pablogsal@gmail.com>
|
|
|
|
| |
comments (GH-17644)
|
|
|
|
| |
regen grammar, opcodes, tokens and symbols (GH-12654)
|
|
|
|
|
|
|
|
|
|
| |
Multiprocessing and concurrent.futures tests now stop the resource
tracker process when tests complete.
Add ResourceTracker._stop() method to
multiprocessing.resource_tracker.
Add _cleanup_tests() helper function to multiprocessing.util: share
code between multiprocessing and concurrent.futures tests.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Each Python subinterpreter now has its own "small integer
singletons": numbers in [-5; 257] range.
It is no longer possible to change the number of small integers at
build time by overriding NSMALLNEGINTS and NSMALLPOSINTS macros:
macros should now be modified manually in pycore_pystate.h header
file.
For now, continue to share _PyLong_Zero and _PyLong_One singletons
between all subinterpreters.
|