[Python-Dev] Impact of Namedtuple on startup time (original) (raw)

Antoine Pitrou antoine at python.org
Mon Jul 17 09:31:35 EDT 2017

Le 17/07/2017 à 15:26, Isaac Morland a écrit :

I think I understand well enough to say something intelligent… While actual references to source are likely rare (certainly I’ve never used it), my understanding is that the way namedtuple works is to construct source, and then exec it to create the class. Once that is done, there is no significant saving to be had by throwing away the constructed source value.

The proposed resolution on https://bugs.python.org/issue28638 is to avoid exec() on most parts of the namedtuple class, hence speeding up the class creation.

I come from a non-Pythonic background so use of exec still feels a bit weird to me but I absolutely love namedtuple and use it constantly.

I think for most Python programmers, it still feels a bit un-Pythonic. While exec() is part of Python, it's generally only used in fringe cases where nothing else works.

Regards

Antoine.

More information about the Python-Dev mailing list