RetroSearch Browse

Mon Nov 29 08:55:13 CET 2010 · https://mail.python.org/pipermail/python-dev/2010-November/106121.html

2010/11/29 "Martin v. Löwis" <martin at v.loewis.de>

> I have now completed
>
> http://www.python.org/dev/peps/pep-0384/

was structseq.h considered?
IMO it could be made PEP384-compliant with two additions that would replace
two non-compliant functions:

- A new function to create types, since PyStructSequence_InitType
is supposed to work on a unititialized static variable:
    PyTypeObject *PyStructSequence_NewType(PyStructSequence_Desc *desc);

- PyStructSequence_SetItem(), similar to the
macro PyStructSequence_SET_ITEM; the PyStructSequence structure should be
hidden.

-- 
Amaury Forgeot d'Arc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20101129/88b0fbb1/attachment.html>

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2010-November/106121.html below:

[Python-Dev] PEP 384 final review