-
-
Notifications
You must be signed in to change notification settings - Fork 31.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
_replace() no longer works on platform.uname_result objects #86329
Comments
Starting from Python 3.9, it seems like the
I'm not sure if this is an intended change or an uninteded side-effect. The
This late resolution is what's new in Python 3.9 and also the source of the issue as far as I can tell. I suppose the answer may depend on how braod our definition of "largely compatible" is. For some context, we use |
Indeed, it was unexpected that consumers of the It should be possible to support Marc, do you have an opinion? |
I filed bpo-42189, which is similar but maybe worse: copy.deepcopy() is broken for platform.uname_result objects. |
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'). |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: