[issue26805] Refer to types.SimpleNamespace in namedtuple documentation

Roundup Robot added the comment: New changeset 3115b6ce1006 by Paul Moore in branch '3.5': Mention types.SimpleNamespace in collections.namedtuple doc https://hg.python.org/cpython/rev/3115b6ce1006 -- ___ Python tracker

[issue26805] Refer to types.SimpleNamespace in namedtuple documentation

Berker Peksag added the comment: Or if you don't want to use any hg extension: hg update 3.5 hg import --no-c http://bugs.python.org/file42520/collections.patch hg commit hg update default hg merge 3.5 hg revert -ar default hg resolve -am hg commit (Null merge (hg merge 3.5 and later) is step d

[issue26805] Refer to types.SimpleNamespace in namedtuple documentation

STINNER Victor added the comment: I don't know what "inactive" means in Mercurial. Python 3.5 is actively developed (maintained): https://docs.python.org/devguide/#status-of-python-branches > How should I do the commit into 3.5? Update to 3.5 (hg up 3.5), transplant your change (hg transplant c

[issue26805] Refer to types.SimpleNamespace in namedtuple documentation

Paul Moore added the comment: Ah, thanks. I probably did the commit the wrong way round in that case, as I committed to tip. How should I do the commit into 3.5? (I'm also somewhat confused by the fact that hg describes the 3.5 branch as "inactive"...) -- _

[issue26805] Refer to types.SimpleNamespace in namedtuple documentation

STINNER Victor added the comment: types.SimpleNamespace is also available on Python 3.5, you may also modify Python 3.5 doc. -- ___ Python tracker ___ __

[issue26805] Refer to types.SimpleNamespace in namedtuple documentation

Changes by Paul Moore : -- resolution: -> fixed stage: needs patch -> resolved status: open -> closed ___ Python tracker ___ ___ Pyth

[issue26805] Refer to types.SimpleNamespace in namedtuple documentation

Roundup Robot added the comment: New changeset c3232d1d8ca0 by Paul Moore in branch 'default': Mention types.SimpleNamespace in collections.namedtuple doc https://hg.python.org/cpython/rev/c3232d1d8ca0 -- nosy: +python-dev ___ Python tracker

[issue26805] Refer to types.SimpleNamespace in namedtuple documentation

Paul Moore added the comment: Thanks Victor. I'll sort this out this evening when I get to my PC with access to the CPython repo. -- ___ Python tracker ___ _

[issue26805] Refer to types.SimpleNamespace in namedtuple documentation

STINNER Victor added the comment: LGTM. I was going to push your sugestion when I saw that you are allowed to push yourself. See my attached patch: * I fixed :ref:`types.SimpleNamespace` => you have to use :class:`...` * I replaced "may be" with "can be" (I'm not confortable with "may", but it'

[issue26805] Refer to types.SimpleNamespace in namedtuple documentation

Changes by Berker Peksag : -- keywords: +easy stage: -> needs patch versions: +Python 3.5 ___ Python tracker ___ ___ Python-bugs-list

[issue26805] Refer to types.SimpleNamespace in namedtuple documentation

Changes by Chris Angelico : -- nosy: +Rosuav ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

[issue26805] Refer to types.SimpleNamespace in namedtuple documentation

New submission from Paul Moore: People often look towards collections.namedtuple when all they actually want is "named attribute" access to a collection of values, without needing a tuple subclass, or positional access. In these cases, types.SimpleNamespace may be a better fit. I suggest addi