[issue38996] introduction of default values for collection.namedtuple

Change by Pablo Galindo Salgado : -- resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker ___ _

[issue38996] introduction of default values for collection.namedtuple

Eric V. Smith added the comment: Agreed on closing this issue. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscr

[issue38996] introduction of default values for collection.namedtuple

Raymond Hettinger added the comment: Here's the status of the various ways to do it: 1) In 3.7, collections.namedtuple() added the *defaults* parameter and the *_field_defaults* attribute. 2) In 3.6.1, typing.NamedTuple added support for default values. 3) In older versions of Python, it wa

[issue38996] introduction of default values for collection.namedtuple

Karthikeyan Singaravelan added the comment: Is it different from the defaults parameter added in 3.7 with https://github.com/python/cpython/commit/3948207c610e931831828d33aaef258185df31db . The linked pypi package seems to do the same thing. -- nosy: +xtreak

[issue38996] introduction of default values for collection.namedtuple

Eric V. Smith added the comment: Is there something that your module can do that typing.NamedTuple can't do? This won't be added to 2.7: 3.9 would be the first possible version to add a feature to. -- assignee: -> rhettinger nosy: +eric.smith, rhettinger versions: -Python 2.7, Pyth

[issue38996] introduction of default values for collection.namedtuple

New submission from Arno-Can Uestuensoez : Hello, I had the requirement to make excessive use of named tuples in an extended way. The applications are variable data sets with optional items. Typical in protocol dat a units, or e.g. mixed abstract filesystem types for heterogeneous file system