mirror of
				https://github.com/python/cpython.git
				synced 2025-10-31 18:28:49 +00:00 
			
		
		
		
	 5376ba9630
			
		
	
	
		5376ba9630
		
	
	
	
	
		
			
			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")
		
	
			
		
			
				
	
	
		
			117 lines
		
	
	
	
		
			2 KiB
		
	
	
	
		
			ReStructuredText
		
	
	
	
	
	
			
		
		
	
	
			117 lines
		
	
	
	
		
			2 KiB
		
	
	
	
		
			ReStructuredText
		
	
	
	
	
	
| .. highlightlang:: c
 | |
| 
 | |
| 
 | |
| .. _concrete:
 | |
| 
 | |
| **********************
 | |
| Concrete Objects Layer
 | |
| **********************
 | |
| 
 | |
| The functions in this chapter are specific to certain Python object types.
 | |
| Passing them an object of the wrong type is not a good idea; if you receive an
 | |
| object from a Python program and you are not sure that it has the right type,
 | |
| you must perform a type check first; for example, to check that an object is a
 | |
| dictionary, use :c:func:`PyDict_Check`.  The chapter is structured like the
 | |
| "family tree" of Python object types.
 | |
| 
 | |
| .. warning::
 | |
| 
 | |
|    While the functions described in this chapter carefully check the type of the
 | |
|    objects which are passed in, many of them do not check for *NULL* being passed
 | |
|    instead of a valid object.  Allowing *NULL* to be passed in can cause memory
 | |
|    access violations and immediate termination of the interpreter.
 | |
| 
 | |
| 
 | |
| .. _fundamental:
 | |
| 
 | |
| Fundamental Objects
 | |
| ===================
 | |
| 
 | |
| This section describes Python type objects and the singleton object ``None``.
 | |
| 
 | |
| .. toctree::
 | |
| 
 | |
|    type.rst
 | |
|    none.rst
 | |
| 
 | |
| 
 | |
| .. _numericobjects:
 | |
| 
 | |
| Numeric Objects
 | |
| ===============
 | |
| 
 | |
| .. index:: object: numeric
 | |
| 
 | |
| .. toctree::
 | |
| 
 | |
|    long.rst
 | |
|    bool.rst
 | |
|    float.rst
 | |
|    complex.rst
 | |
| 
 | |
| 
 | |
| .. _sequenceobjects:
 | |
| 
 | |
| Sequence Objects
 | |
| ================
 | |
| 
 | |
| .. index:: object: sequence
 | |
| 
 | |
| Generic operations on sequence objects were discussed in the previous chapter;
 | |
| this section deals with the specific kinds of sequence objects that are
 | |
| intrinsic to the Python language.
 | |
| 
 | |
| .. XXX sort out unicode, str, bytes and bytearray
 | |
| 
 | |
| .. toctree::
 | |
| 
 | |
|    bytes.rst
 | |
|    bytearray.rst
 | |
|    unicode.rst
 | |
|    tuple.rst
 | |
|    list.rst
 | |
| 
 | |
| 
 | |
| .. _mapobjects:
 | |
| 
 | |
| Container Objects
 | |
| =================
 | |
| 
 | |
| .. index:: object: mapping
 | |
| 
 | |
| .. toctree::
 | |
| 
 | |
|    dict.rst
 | |
|    set.rst
 | |
| 
 | |
| 
 | |
| .. _otherobjects:
 | |
| 
 | |
| Function Objects
 | |
| ================
 | |
| 
 | |
| .. toctree::
 | |
| 
 | |
|    function.rst
 | |
|    method.rst
 | |
|    cell.rst
 | |
|    code.rst
 | |
| 
 | |
| 
 | |
| Other Objects
 | |
| =============
 | |
| 
 | |
| .. toctree::
 | |
| 
 | |
|    file.rst
 | |
|    module.rst
 | |
|    iterator.rst
 | |
|    descriptor.rst
 | |
|    slice.rst
 | |
|    memoryview.rst
 | |
|    weakref.rst
 | |
|    capsule.rst
 | |
|    gen.rst
 | |
|    coro.rst
 | |
|    datetime.rst
 | |
| 
 |