| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
The existing volatile `left`/`right` pointers guarantee that the reads will all occur, but does not guarantee that they will be _used_. So a compiler can still short-circuit the loop, saving e.g. the overhead of doing the xors and especially the overhead of the data dependency between `result` and the reads. That would change performance depending on where the first unequal byte occurs. This change removes that optimization.
(This is change GH-1 from https://bugs.python.org/issue40791 .)
(cherry picked from commit 31729366e2bc09632e78f3896dbce0ae64914f28)
Co-authored-by: Devin Jeanpierre <jeanpierreda@google.com>
|
| |
|
|
|
| |
(cherry picked from commit 5b83ef71d3060e1651d3680e805f13a1049c7d6d)
Co-authored-by: Zackery Spytz <zspytz@gmail.com>
|
| |
|
|
|
| |
Error messages when pass keyword arguments to some builtins that
don't support keyword arguments contained double parenthesis: "()()".
The regression was introduced by bpo-30534.
|
| |
|
|
| |
_PyArg_NoPositional() now are macros.
|
| |
|
|
| |
Patch by Tal Einat.
|
| |
|
|
| |
dict.
|
| | |
|
| |\ |
|
| | | |
|
| | |
| |
| |
| | |
itemgetter, attrgetter and methodcaller objects.
|
| | |
| |
| |
| | |
silently ignore keyword arguments.
|
| | | |
|
| | |
| |
| |
| |
| | |
module now support pickling. Added readable and evaluable repr for these
objects. Based on patch by Josh Rosenberg.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Some time ago we changed the docs to consistently use the term 'bytes-like
object' in all the contexts where bytes, bytearray, memoryview, etc are used.
This patch (by Ezio Melotti) completes that work by changing the error
messages that previously reported that certain types did "not support the
buffer interface" to instead say that a bytes-like object is required. (The
glossary entry for bytes-like object references the discussion of the buffer
protocol in the docs.)
|
| |\ \
| |/ |
|
| | | |
|
| |/ |
|
| | |
|
|
|
Patch by Zachary Ware.
|