[issue12412] non defined representation for pwd.struct_passwd

Éric Araujo added the comment: Actually, I’ve found that there are some structseq’s repr that get tested in the CPython test suite. -- ___ Python tracker ___ __

[issue12412] non defined representation for pwd.struct_passwd

R. David Murray added the comment: But pypy passed the attribute access tests in the test suite? -- ___ Python tracker ___ ___ Python

[issue12412] non defined representation for pwd.struct_passwd

Amaury Forgeot d'Arc added the comment: pypy did not use a structseq in this case. Fixed in (pypy's repo) dded6e510044 -- nosy: +amaury.forgeotdarc ___ Python tracker ___ __

[issue12412] non defined representation for pwd.struct_passwd

Éric Araujo added the comment: The docs indeed don’t say more that “Password database entries are reported as a tuple-like object, whose attributes correspond to the members of the passwd structure”; no mention is made of named tuple or struct sequence. I think there is no bug for CPython; yo

[issue12412] non defined representation for pwd.struct_passwd

R. David Murray added the comment: Looks like the difference between a regular tuple and a named tuple. The correct test is to access the members using the names, and the test suite currently does this. The repr shouldn't, I think, be required to be identical. On the other hand, if pypy is

[issue12412] non defined representation for pwd.struct_passwd

New submission from Francisco Garcia : pwd.struct_passwd has different representations in cpython 2.7.2 and pypy 1.5 A unit test from cpython might enforce the same representation across interpreters: >>> print pwd.getpwuid(os.getuid()) Current cpython output: pwd.struct_passwd(pw_name='demo