j: Next unread message
k: Previous unread message
j a: Jump to all threads
j l: Jump to MailingList overview
Oh, about the cost of writing C code, we started to enhance the socket module in socket.py but keep the C code unchanged. I am thinking to the support of enums. Some C functions are wrapped in Python.
Le 19 juin 2017 11:59 PM, "Guido van Rossum" email@example.com a écrit :
There are examples in timemodule.c which went through a similar conversion from plain tuples to (sort-of) named tuples. I agree that upgrading the tuples returned by the socket module to named tuples would be nice, but it's a low priority project. Maybe someone interested can create a PR? (First open an issue stating that you're interested; point to this email from me to prevent that some other core dev just closes it again.)
On Mon, Jun 19, 2017 at 2:24 PM, Victor Stinner firstname.lastname@example.org wrote:
2017-06-13 22:13 GMT+02:00 Thomas Güttler email@example.com:
AFAIK the socket module returns plain tuples in Python3:
Why not use named tuples?
For technical reasons: the socket module is mostly implemented in the C language, and define a "named tuple" in C requires to implement a "sequence" time which requires much more code than creating a tuple.
In short, create a tuple is as simple as Py_BuildValue("OO", item1, item2).
Creating a "sequence" type requires something like 50 lines of code, maybe more, I don't know exactly.
Python-ideas mailing list Pythonfirstname.lastname@example.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/
-- --Guido van Rossum (python.org/~guido)