This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author jaraco
Recipients jaraco, lemburg, steven.daprano
Date 2021-03-05.01:10:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1614906603.85.0.591393626285.issue40578@roundup.psfhosted.org>
In-reply-to
Content
For posterity, I'll share my motivation.

> Why is it a problem that people are using something which is documented as a tuple?

It's not a problem that they access it by tuple if it's documented.

The problem is that it's documented for access as a tuple when there is a superior method to access (by attribute) that's less opaque than the historical method by index.

I apologize for not documenting that in the original post. It seemed obvious to me at the time that having one obvious way to access the items would be preferred.

For example, `uname()[0]` doesn't mean anything to me without a comment or referencing the documetation, whereas `uname().system` does.

Access by numerical index hearkens back to C-style arrays and in my mind is an anti-pattern.
History
Date User Action Args
2021-03-05 01:10:03jaracosetrecipients: + jaraco, lemburg, steven.daprano
2021-03-05 01:10:03jaracosetmessageid: <1614906603.85.0.591393626285.issue40578@roundup.psfhosted.org>
2021-03-05 01:10:03jaracolinkissue40578 messages
2021-03-05 01:10:02jaracocreate