RetroSearch Browse

Mon Nov 29 09:09:14 CET 2010 · https://mail.python.org/pipermail/python-dev/2010-November/106122.html

>     I have now completed
> 
>     http://www.python.org/dev/peps/pep-0384/
> 
> 
> was structseq.h considered?

No, it wasn't - unfortunately, it still doesn't get included when
including Python.h. I'll add it.

> 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.

Sounds good.

Regards,
Martin

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

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

[Python-Dev] PEP 384 final review