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
Date 2020-05-09.14:06:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1589033216.57.0.707246281717.issue40578@roundup.psfhosted.org>
In-reply-to
Content
In issue40570, I learned that some users are still relying on legacy tuple-like behaviors of `platform.uname()`, namely the access by item position and length:

```
platform.uname()[0]
len(platform.uname())
```

I propose to deprecate these behaviors and constrain the supported interface to the following:

```
platform.uname().attribute
items = tuple(platform.uname())
```

In other words, the `uname_result` would only support access of the items by attribute or iteration of all attributes.

Any users wishing to access items by position or to calculate the length of the result would need to explicitly construct a tuple from the result.
History
Date User Action Args
2020-05-09 14:06:56jaracosetrecipients: + jaraco, lemburg
2020-05-09 14:06:56jaracosetmessageid: <1589033216.57.0.707246281717.issue40578@roundup.psfhosted.org>
2020-05-09 14:06:56jaracolinkissue40578 messages
2020-05-09 14:06:56jaracocreate