[issue42163] _replace() no longer works on platform.uname_result objects

Change by Jason R. Coombs : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue42163] _replace() no longer works on platform.uname_result objects

Jason R. Coombs added the comment: New changeset 799722cb0ddb90752cde7798cab543f30623ebf2 by Jason R. Coombs in branch '3.9': [3.9] bpo-42163, bpo-42189, bpo-42659: Support uname_tuple._replace (for all but processor) (GH-23010) (#24232)

[issue42163] _replace() no longer works on platform.uname_result objects

Change by Jason R. Coombs : -- pull_requests: +23055 pull_request: https://github.com/python/cpython/pull/24232 ___ Python tracker ___

[issue42163] _replace() no longer works on platform.uname_result objects

Jason R. Coombs added the comment: New changeset a6fd0f414c0cb4cd5cc20eb2df3340b31c6f7743 by Jason R. Coombs in branch 'master': bpo-42163, bpo-42189, bpo-42659: Support uname_tuple._replace (for all but processor) (#23010)

[issue42163] _replace() no longer works on platform.uname_result objects

Jason R. Coombs added the comment: Please take a look at the PR. Let me know what you think about the limited compatibility it adds (still doesn't allow _replace on 'processor'). -- ___ Python tracker

[issue42163] _replace() no longer works on platform.uname_result objects

Robert O'Callahan added the comment: I filed issue 42189, which is similar but maybe worse: copy.deepcopy() is broken for platform.uname_result objects. -- nosy: +rocallahan ___ Python tracker

[issue42163] _replace() no longer works on platform.uname_result objects

Change by Jason R. Coombs : -- keywords: +patch pull_requests: +21926 stage: -> patch review pull_request: https://github.com/python/cpython/pull/23010 ___ Python tracker ___

[issue42163] _replace() no longer works on platform.uname_result objects

Jason R. Coombs added the comment: Indeed, it was unexpected that consumers of the `uname_result` were using `_replace`. In fact, the focus of the tests is on ensuring that users are able to access the items by index, e.g. `uname()[0]`. It should be possible to support `_replace` on the

[issue42163] _replace() no longer works on platform.uname_result objects

Change by Jason R. Coombs : -- assignee: -> jaraco ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue42163] _replace() no longer works on platform.uname_result objects

Change by Serhiy Storchaka : -- nosy: +jaraco, rhettinger ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue42163] _replace() no longer works on platform.uname_result objects

New submission from Chandan Singh : Starting from Python 3.9, it seems like the `_replace()` method no longer works on `platform.uname_result` objects, that are returned by `platform.uname()`. A simple example can be seen below, which works on Python 3.8, but not on Python 3.9. ``` >>>