| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
optional (GH-15851)
|
|
|
|
| |
copy.copy() (GH-12995)
|
| |
|
| |
|
| |
|
|
|
| |
In text mode, the "size" parameter indicates the number of characters, not bytes.
|
| |
|
|
|
|
|
|
|
|
|
| |
In the table model used by docutils, the `cols` attribute of `tgroup`
nodes is mandatory, see [1]. It is used in texinfo builder in [2].
[1]: https://www.oasis-open.org/specs/tm9901.htm#AEN348
[2]: https://github.com/sphinx-doc/sphinx/blob/v2.1.2/sphinx/writers/texinfo.py#L1129
* Doc: Add texinfo support to the Makefile
|
| |
|
| |
|
|
|
| |
https://gitlab.com/python-devs/importlib_metadata/-/tags/0.21
|
| |
|
|
|
|
| |
toolset installed (GH-15849)
|
| |
|
|
|
|
|
| |
It looks like "cryptographically strong" is the preferred phrase from the surrounding documentation.
Automerge-Triggered-By: @tiran
|
| |
|
|
|
|
|
|
|
|
| |
* Optimize sum() for bools.
* Fix sum([], False).
* Add a NEWS entry.
|
|
|
|
|
|
|
|
| |
* Improve doc on open's mode +
* Improve wording
* Address comment from Rémi
|
|
|
|
|
|
|
|
|
|
| |
Makes the pwd module PEP-384 compatible
https://bugs.python.org/issue38073
Automerge-Triggered-By: @tiran
|
|
|
|
|
|
| |
feed_eof(), feed_data(), set_exception(), and set_transport() are prefixed with underscore now.
https://bugs.python.org/issue38066
|
|
|
|
|
| |
configparser (GH-6137)
Document how $ and % can be escaped in configparser.
|
|
|
|
| |
(GH-11836)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
[queue] (GH-13950)
This PR deprecate explicit loop parameters in all public asyncio APIs
This issues is split to be easier to review.
fourth step: queue.py
https://bugs.python.org/issue36373
|
|
|
|
| |
type (GH-14836)
|
|
|
|
|
|
|
|
|
|
| |
Add functions with various calling conventions to `_testcapi`, expose them as module-level functions, bound methods, class methods, and static methods, and test calling them and introspecting them through GDB.
https://bugs.python.org/issue37499
Co-authored-by: Jeroen Demeyer <J.Demeyer@UGent.be>
Automerge-Triggered-By: @pganssle
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Summary:
Eliminate uses of `_Py_IDENTIFIER` from `_posixsubprocess`, replacing them with interned strings.
Also tries to find an existing version of the module, which will allow subinterpreters.
https://bugs.python.org/issue38069
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
[locks] (GH-13920)
This PR deprecate explicit loop parameters in all public asyncio APIs
This issues is split to be easier to review.
Third step: locks.py
https://bugs.python.org/issue36373
|
| |
|
|
|
| |
Assume gettimeofday exists and takes two arguments.
|
|
|
|
|
|
|
|
| |
(GH-14660)
Add examples for mocking asynchronous iterators and asynchronous context managers.
https://bugs.python.org/issue37052
|
|
|
|
| |
Make the termios module PEP-384 compatible.
|
|
|
|
| |
Make the grp module PEP-384 compliant.
|
|
|
|
| |
As described in Doc/c-api/init.rst, PyEval_InitThreads() cannot be called
before Py_Initialize() function.
|
|
|
| |
Azure runs macOS, so we don't need Travis to do it.
|
| |
|
|
|
|
| |
Updated zlibmodule.c to be PEP 384 compliant.
|
|
|
|
|
|
|
|
|
|
| |
* PEP-384 _struct
* More PEP-384 fixes for _struct
Summary: Add a couple of more fixes for `_struct` that were previously missed such as removing `tp_*` accessors and using `PyBytesWriter` instead of calling `PyBytes_FromStringAndSize` with `NULL`. Also added a test to confirm that `iter_unpack` type is still uninstantiable.
* 📜🤖 Added by blurb_it.
|
|
|
|
|
| |
* Use the const qualifier for constant C strings.
* Intern field and attribute names.
* Temporary incref a borrowed reference to a list item.
|
| |
|
|
|
|
|
| |
Change "clean" makefile target to also clean the program guided
optimization (PGO) data. Previously you would have to use "make
clean" and "make profile-removal", or "make clobber".
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Having these in a separate file from the one that's named after the
module in the usual way makes it very easy to miss them when looking
for tests for these two functions.
(In fact when working recently on is_normalized, I'd been surprised to
see no tests for it here and concluded the function had evaded being
tested at all. I'd gone as far as to write up some tests myself
before I spotted this other file.)
Mostly this just means moving all the one file's code into the other,
and moving code from the module toplevel to inside the test class to
keep it tidily separate from the rest of the file's code.
There's one substantive change, which reduces by a bit the amount of
code to be moved: we drop the `x > sys.maxunicode` conditional and all
the `RangeError` logic behind it. Now if that condition ever occurs
it will cause an error at `chr(x)`, and a test failure. That's the
right result because, since PEP 393 in Python 3.3, there is no longer
such a thing as an "unsupported character".
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is the sort of `goto` that requires the reader to stare hard at
the code to unpick what it's doing.
On doing so, the answer is... not very much!
* It jumps from the bottom of the loop to almost the top; the effect
is to bypass the loop condition `s < end` and also the
`if`-condition `*s != '\\'`, acting as if both are true.
* We've just decremented `s`, after incrementing it in the `switch`
condition. So it has the same value as when `s == end` failed.
Before that was another increment... and before that we had
`s < end`. So `s < end` true, then increment, then `s == end`
false... that means `s < end` is still true.
* Also this means `s` points to the same character as it did for the
`switch` condition. And there was a `case '\\'`, which we didn't
hit -- so `*s != '\\'` is also true.
* That means this has no effect on the behavior! The most it might do
is an optimization -- we get to skip those two checks, because (as
just proven above) we know they're true.
* But gosh, this is the *invalid escape sequence* path. This does not
seem like the kind of code path that calls for extreme optimization
tricks.
So, take the `goto` and the label out.
Perhaps the compiler will notice the exact same facts we showed above,
and generate identical code. Or perhaps it won't! That'll be OK.
But then, crucially, if some future edit to this loop causes the
reasoning above to *stop* holding true... the compiler will adjust
this jump accordingly. One of us fallible humans might not.
|
| |
|
|
|
|
| |
This only happened when initializing the subprocess to run a module.
This recent bug only affected 3.7.4 and 3.8.0b2 to 3.8.0b4.
|
|
|
|
|
| |
The "A4" pdfs were previously the wrong size due to a change in the options in Sphinx 1.5.
See also sphinx-doc/sphinx#5235
|
|
|
|
| |
(GH-14431)
|
| |
|