| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
collection) in collections.OrderedDict constructor.
Patch reviewed by Serhiy Storchaka.
|
|
|
|
| |
Original patch by Martin Panter.
|
| |
|
|\ |
|
| |
| |
| |
| | |
Initial patch by Kinga Farkas, Martin Panter, and John Posner.
|
| |
| |
| |
| | |
for single-byte argument on Linux.
|
| | |
|
|\ \
| |/ |
|
| |\ |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Patch by Benno Leslie and Yury Selivanov.
|
|\ \ \
| |/ /
| | |
| | |
| | | |
object now always allocates place for trailing null byte and it's buffer now
is always null-terminated.
|
| | |
| | |
| | |
| | |
| | | |
object now always allocates place for trailing null byte and it's buffer now
is always null-terminated.
|
| | | |
|
| | |
| | |
| | |
| | | |
Patch by Martin Panter.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Summary of changes:
1. Coroutines now have a distinct, separate from generators
type at the C level: PyGen_Type, and a new typedef PyCoroObject.
PyCoroObject shares the initial segment of struct layout with
PyGenObject, making it possible to reuse existing generators
machinery. The new type is exposed as 'types.CoroutineType'.
As a consequence of having a new type, CO_GENERATOR flag is
no longer applied to coroutines.
2. Having a separate type for coroutines made it possible to add
an __await__ method to the type. Although it is not used by the
interpreter (see details on that below), it makes coroutines
naturally (without using __instancecheck__) conform to
collections.abc.Coroutine and collections.abc.Awaitable ABCs.
[The __instancecheck__ is still used for generator-based
coroutines, as we don't want to add __await__ for generators.]
3. Add new opcode: GET_YIELD_FROM_ITER. The opcode is needed to
allow passing native coroutines to the YIELD_FROM opcode.
Before this change, 'yield from o' expression was compiled to:
(o)
GET_ITER
LOAD_CONST
YIELD_FROM
Now, we use GET_YIELD_FROM_ITER instead of GET_ITER.
The reason for adding a new opcode is that GET_ITER is used
in some contexts (such as 'for .. in' loops) where passing
a coroutine object is invalid.
4. Add two new introspection functions to the inspec module:
getcoroutinestate(c) and getcoroutinelocals(c).
5. inspect.iscoroutine(o) is updated to test if 'o' is a native
coroutine object. Before this commit it used abc.Coroutine,
and it was requested to update inspect.isgenerator(o) to use
abc.Generator; it was decided, however, that inspect functions
should really be tailored for checking for native types.
6. sys.set_coroutine_wrapper(w) API is updated to work with only
native coroutines. Since types.coroutine decorator supports
any type of callables now, it would be confusing that it does
not work for all types of coroutines.
7. Exceptions logic in generators C implementation was updated
to raise clearer messages for coroutines:
Before: TypeError("generator raised StopIteration")
After: TypeError("coroutine raised StopIteration")
|
|\ \ \
| |/ / |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Patch from Petr Viktorin.
|
| | |
| | |
| | |
| | |
| | | |
return True when finding the empty string and the indexes are completely out
of range.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Something went horribly wrong when I was doing `hg rebase`.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
PyObject_IsInstance(), PyObject_RichCompareBool() and _PyDict_Contains()
to check for and handle errors correctly.
|
| |\ \ \
| | |/ /
| | | |
| | | |
| | | | |
PyObject_IsInstance(), PyObject_RichCompareBool() and _PyDict_Contains()
to check for and handle errors correctly.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
PyObject_IsInstance(), PyObject_RichCompareBool() and _PyDict_Contains()
to check for and handle errors correctly.
|
|\ \ \ \
| |/ / /
| | | |
| | | | |
signatures as booleans.
|
| | | |
| | | |
| | | |
| | | | |
signatures as booleans.
|
| | | | |
|
| | | | |
|
|\ \ \ \
| |/ / / |
|
| | | | |
|
|/ / /
| | |
| | |
| | | |
function.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- missing DECREF in PyModule_FromDefAndSpec2
- missing DECREF in PyType_FromSpecAndBases2
- missing DECREF in _testmultiphase module
Patch by Petr Viktorin
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Known limitations of the current implementation:
- documentation changes are incomplete
- there's a reference leak I haven't tracked down yet
The leak is most visible by running:
./python -m test -R3:3 test_importlib
However, you can also see it by running:
./python -X showrefcount
Importing the array or _testmultiphase modules, and
then deleting them from both sys.modules and the local
namespace shows significant increases in the total
number of active references each cycle. By contrast,
with _testcapi (which continues to use single-phase
initialisation) the global refcounts stabilise after
a couple of cycles.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Raise PendingDeprecationWarning when generator raises StopIteration
and no __future__ import is used. Fix offenders in the stdlib
and tests.
See also issue 22906.
Thanks to Nick Coghlan and Berker Peksag for reviews.
|
|\ \ \
| |/ /
| | |
| | |
| | | |
Fixed segmentation fault in sqlite3.Row constructor with faked cursor type.
Fixed system error in the comparison of faked types.SimpleNamespace.
|