mirror of
https://github.com/python/cpython.git
synced 2025-11-25 21:11:09 +00:00
Python 3.9.0a1
This commit is contained in:
parent
24555ce2f9
commit
fd757083df
573 changed files with 6113 additions and 1382 deletions
|
|
@ -1,2 +0,0 @@
|
|||
Use singular/plural noun in error message when instantiating an abstract
|
||||
class with non-overriden abstract method(s).
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Convert posixmodule.c statically allocated types ``DirEntryType`` and
|
||||
``ScandirIteratorType`` to heap-allocated types.
|
||||
|
|
@ -1 +0,0 @@
|
|||
Fix the cast on error in :c:func:`PyLong_AsUnsignedLongLongMask()`.
|
||||
|
|
@ -1,6 +0,0 @@
|
|||
Add a new public :c:func:`PyObject_CallNoArgs` function to the C API: call a
|
||||
callable Python object without any arguments. It is the most efficient way to
|
||||
call a callback without any argument. On x86-64, for example,
|
||||
``PyObject_CallFunctionObjArgs(func, NULL)`` allocates 960 bytes on the stack
|
||||
per call, whereas ``PyObject_CallNoArgs(func)`` only allocates 624 bytes per
|
||||
call.
|
||||
|
|
@ -1 +0,0 @@
|
|||
Fix dtrace issue introduce by bpo-36842
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
The new function :c:func:`PyCode_NewWithPosOnlyArgs` allows to create
|
||||
code objects like :c:func:`PyCode_New`, but with an extra *posonlyargcount*
|
||||
parameter for indicating the number of positonal-only arguments.
|
||||
|
|
@ -1 +0,0 @@
|
|||
The :const:`METH_FASTCALL` calling convention has been documented.
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Add fast functions for calling methods: :c:func:`_PyObject_VectorcallMethod`,
|
||||
:c:func:`_PyObject_CallMethodNoArgs` and :c:func:`_PyObject_CallMethodOneArg`.
|
||||
|
|
@ -1 +0,0 @@
|
|||
Add :func:`PyConfig_SetWideStringList` function.
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Add new function ``_PyObject_CallOneArg`` for calling an object with one
|
||||
positional argument.
|
||||
|
|
@ -1 +0,0 @@
|
|||
Exclude Python-ast.h, ast.h and asdl.h from the limited API.
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
The vectorcall protocol is now enabled for ``type`` objects: set
|
||||
``tp_vectorcall`` to a vectorcall function to be used instead of ``tp_new``
|
||||
and ``tp_init`` when calling the class itself.
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
The vectorcall protocol now requires that the caller passes only strings as
|
||||
keyword names.
|
||||
|
|
@ -1 +0,0 @@
|
|||
``PyCFunction_Call`` is now a deprecated alias of :c:func:`PyObject_Call`.
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
The functions ``PyEval_CallObject``, ``PyEval_CallFunction``,
|
||||
``PyEval_CallMethod`` and ``PyEval_CallObjectWithKeywords`` are deprecated.
|
||||
Use :c:func:`PyObject_Call` and its variants instead.
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Add :c:func:`_PyObject_FunctionStr` to get a user-friendly string representation
|
||||
of a function-like object. Patch by Jeroen Demeyer.
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Fix subtype_dealloc to suppress the type decref when the base type is a C
|
||||
heap type
|
||||
|
|
@ -1 +0,0 @@
|
|||
Fix a crash in ``PySys_SetArgvEx(0, NULL, 0)``.
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Options added by ``PySys_AddXOption()`` are now handled the same way than
|
||||
``PyConfig.xoptions`` and command line ``-X`` options.
|
||||
|
|
@ -1,4 +0,0 @@
|
|||
The C function ``PyGen_NeedsFinalizing`` has been removed. It was not
|
||||
documented, tested or used anywhere within CPython after the implementation
|
||||
of :pep:`442`. Patch by Joannah Nanjekye.
|
||||
(Patch by Joannah Nanjekye)
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Make dict and weakref offsets opaque for C heap types by passing the offsets
|
||||
through PyMemberDef
|
||||
|
|
@ -1 +0,0 @@
|
|||
The :c:func:`Py_UNREACHABLE` macro now calls :c:func:`Py_FatalError`.
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
Python ignored arguments passed to :c:func:`Py_SetPath`,
|
||||
:c:func:`Py_SetPythonHome` and :c:func:`Py_SetProgramName`: fix Python
|
||||
initialization to use specified arguments.
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
:c:func:`Py_SetPath` now sets :data:`sys.executable` to the program full
|
||||
path (:c:func:`Py_GetProgramFullPath`) rather than to the program name
|
||||
(:c:func:`Py_GetProgramName`).
|
||||
|
|
@ -1 +0,0 @@
|
|||
Update audioop extension module to use the stable ABI (PEP-384). Patch by Tyler Kieft.
|
||||
|
|
@ -1 +0,0 @@
|
|||
Revert the removal of PyThreadState_DeleteCurrent() with documentation.
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
The ``_PyObject_CheckConsistency()`` function is now also available in release
|
||||
mode. For example, it can be used to debug a crash in the ``visit_decref()``
|
||||
function of the GC.
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
Fix a crash in :class:`weakref.proxy` objects due to incorrect lifetime
|
||||
management when calling some associated methods that may delete the last
|
||||
reference to object being referenced by the proxy. Patch by Pablo Galindo.
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
Fixed possible leak in :c:func:`PyArg_Parse` and similar functions for
|
||||
format units ``"es#"`` and ``"et#"`` when the macro
|
||||
:c:macro:`PY_SSIZE_T_CLEAN` is not defined.
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
The global variable :c:data:`PyStructSequence_UnnamedField` is now a
|
||||
constant and refers to a constant string.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
Provide :c:func:`Py_EnterRecursiveCall` and :c:func:`Py_LeaveRecursiveCall`
|
||||
as regular functions for the limited API. Previously, there were defined as
|
||||
macros, but these macros didn't work with the limited API which cannot access
|
||||
``PyThreadState.recursion_depth`` field. Remove ``_Py_CheckRecursionLimit``
|
||||
from the stable ABI.
|
||||
|
|
@ -1 +0,0 @@
|
|||
Reëxport some function compatibility wrappers for macros in ``pythonrun.h``.
|
||||
Loading…
Add table
Add a link
Reference in a new issue