[issue5336] collections.namedtuple generates code causing PyChecker warnings

Raymond Hettinger added the comment: Fixed in r70106 and r70121 as part of converting _asdict() to return an OrderedDictionary. Leaving 2.6 and 3.0 as-is. -- resolution: -> fixed status: open -> closed versions: +Python 2.7, Python 3.1 -Python 2.6

[issue5336] collections.namedtuple generates code causing PyChecker warnings

Nick Coghlan added the comment: Completely unrelated to the topic at hand, but that command line can be written more concisely as: E:\Python26\python.exe -m pychecker.checker test.py (pychecker was actually the number 1 use case when it came to justifying the expansion of -m to modules inside

[issue5336] collections.namedtuple generates code causing PyChecker warnings

Raymond Hettinger added the comment: Will look at this one. Am initially disinclined to change _asdict() because I like its compact presentation. -- priority: -> low ___ Python tracker ___

[issue5336] collections.namedtuple generates code causing PyChecker warnings

Changes by Benjamin Peterson : -- assignee: -> rhettinger nosy: +rhettinger ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue5336] collections.namedtuple generates code causing PyChecker warnings

New submission from Mikhail Bessonov : The first argument of some methods generated by collections.namedtuple differs from 'self'. It upsets a number of code checkers, notably PyChecker, because in most cases it is indeed an error. As a result, the code using collections.namedtuple does not pa