-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Fix pickling of NLayout
(backport #12298)
#12299
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
Conversation
Cherry-pick of 136548c has failed:
To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally |
Thank you for opening a new pull request. Before your PR can be merged it will first need to pass continuous integration tests and be reviewed. Sometimes the review process can be slow, so please be patient. While you're waiting, please feel free to review other open PRs. While only a subset of people are authorized to approve pull requests for merging, everyone is encouraged to review open pull requests. Doing reviews helps reduce the burden on the core team and helps make the project's code better for everyone. One or more of the the following people are requested to review this:
|
fb38c26
to
3ec5c34
Compare
Previously the module of this was set incorrectly (stemming from its move in gh-9064), at which point the `__getstate__`/`__setstate__` pickling wouldn't work correctly any more. Also, however, there was no `__getnewargs__` and `new` didn't have a zero-argument form, so this wouldn't have worked either.
3ec5c34
to
19fab65
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Quick detour from pushing the wrong HEAD to this ref, but we're back.
Pull Request Test Coverage Report for Build 8840591157Details
💛 - Coveralls |
Summary
Previously the module of this was set incorrectly (stemming from its move in gh-9064), at which point the
__getstate__
/__setstate__
pickling wouldn't work correctly any more. Also, however, there was no__getnewargs__
andnew
didn't have a zero-argument form, so this wouldn't have worked either.Details and comments
No changelog because this is a private class, and it doesn't actually seem to be causing us problems.
This is an automatic backport of pull request #12298 done by Mergify.