Skip to content

None.__ne__(None) should be NotImplemented #5124

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

evanrittenhouse
Copy link
Contributor

This was changed in Python 3.12. Closes #5103

@evanrittenhouse evanrittenhouse force-pushed the evanrittenhouse/none_ne_notimplemented branch from 4b667ee to ad59192 Compare November 26, 2023 16:49
@evanrittenhouse evanrittenhouse force-pushed the evanrittenhouse/none_ne_notimplemented branch 3 times, most recently from fe2ae32 to 6b4e7c4 Compare December 2, 2023 19:03
@King44447

This comment was marked as spam.

@evanrittenhouse evanrittenhouse force-pushed the evanrittenhouse/none_ne_notimplemented branch 5 times, most recently from 2be96c1 to 5c7d042 Compare December 9, 2023 03:59
@evanrittenhouse
Copy link
Contributor Author

@youknowone this is ready now, but I'm not sure why tests failed on wasm-wasi.

@evanrittenhouse evanrittenhouse marked this pull request as ready for review December 9, 2023 04:21
@evanrittenhouse evanrittenhouse force-pushed the evanrittenhouse/none_ne_notimplemented branch from 5c7d042 to d5cbf76 Compare December 9, 2023 04:52
Copy link
Member

@youknowone youknowone left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for contributing! It looks almost perfect. I left a few nitpicks.

@evanrittenhouse
Copy link
Contributor Author

Done - thanks @youknowone!

@youknowone
Copy link
Member

Could you also check clippy errors? To check it, see the 'Details' of ubuntu-latest build.
Rebasing the patch on RustPython/RustPython main will also fix other CI failures unrelated to this patch.

I am really sorry for late response during you are writing this patch. And thank you so much for contributing.

@evanrittenhouse evanrittenhouse force-pushed the evanrittenhouse/none_ne_notimplemented branch from 1ead4c5 to 63026c3 Compare December 29, 2023 04:39
@evanrittenhouse
Copy link
Contributor Author

Weird, now it's failing on a manual hash implementation? I've rebased against main though

@youknowone
Copy link
Member

That's due to recent Rust version upgrade. I fixed it on main branch. rebasing on main again will fix it.

@evanrittenhouse evanrittenhouse force-pushed the evanrittenhouse/none_ne_notimplemented branch from 63026c3 to 0ac64e1 Compare January 8, 2024 04:47
@evanrittenhouse
Copy link
Contributor Author

Sorry, must've missed your comment - rebased

Copy link
Member

@youknowone youknowone left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, thank you for contributing!

@youknowone youknowone merged commit 1ab133d into RustPython:main Jan 8, 2024
@evanrittenhouse evanrittenhouse deleted the evanrittenhouse/none_ne_notimplemented branch January 8, 2024 14:54
@moreal moreal mentioned this pull request Apr 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None.__ne__(None) behavior is changed in 3.12
3 participants