diff options
author | R David Murray <rdmurray@bitdance.com> | 2014-02-22 21:02:22 (GMT) |
---|---|---|
committer | R David Murray <rdmurray@bitdance.com> | 2014-02-22 21:02:22 (GMT) |
commit | 237fda2984f1e5032936895ad95089abc4a88473 (patch) | |
tree | 4af215667b4c1ab5735dda8124cfa8b07a712273 | |
parent | 7c12432fe1db41ea31ec3af9610a5bc4c372c65c (diff) | |
download | cpython-237fda2984f1e5032936895ad95089abc4a88473.zip cpython-237fda2984f1e5032936895ad95089abc4a88473.tar.gz cpython-237fda2984f1e5032936895ad95089abc4a88473.tar.bz2 |
whatsnew: PyStructSequence_InitType2, Victor's MemoryError fixes.
I'm documenting this new function, but I'm wondering if this will trigger
someone to think about whether or not this actually makes sense :)
-rw-r--r-- | Doc/c-api/tuple.rst | 8 | ||||
-rw-r--r-- | Doc/whatsnew/3.4.rst | 8 |
2 files changed, 16 insertions, 0 deletions
diff --git a/Doc/c-api/tuple.rst b/Doc/c-api/tuple.rst index 184affb..0876739 100644 --- a/Doc/c-api/tuple.rst +++ b/Doc/c-api/tuple.rst @@ -129,6 +129,14 @@ type. Initializes a struct sequence type *type* from *desc* in place. +.. c:function:: void PyStructSequence_InitType2(PyTypeObject *type, PyStructSequence_Desc *desc) + + The same as ``PyStructSequence_InitType``, but returns ``0`` on success and ``-1`` on + failure. + + .. versionadded:: 3.4 + + .. c:type:: PyStructSequence_Desc Contains the meta information of a struct sequence type to create. diff --git a/Doc/whatsnew/3.4.rst b/Doc/whatsnew/3.4.rst index d324879..bbedddd 100644 --- a/Doc/whatsnew/3.4.rst +++ b/Doc/whatsnew/3.4.rst @@ -1421,6 +1421,10 @@ Other Build and C API Changes specifications for ``%s``, ``%A``, ``%U``, ``%V``, ``%S``, and ``%R``. (Contributed by Ysj Ray and Victor Stinner in :issue:`7330`.) +* New function :c:func:`PyStructSequence_InitType2` supplements the + existing :c:func:`PyStructSequence_InitType` function. The difference + is that it returns ``0`` on success and ``-1`` on failure. + .. _other-improvements-3.4: @@ -1466,6 +1470,10 @@ Other Improvements uses of :ref:`__prepare__ <prepare>`. (Contributed by Benjamin Peterson in :issue:`17853`.) +* A number of MemoryError-related crashes were identified and fixed by Victor + Stinner using his :pep:`445`-based ``pyfailmalloc`` tool (:issue:`18408`, + :issue:`18520`). + Significant Optimizations ------------------------- |