-
-
Notifications
You must be signed in to change notification settings - Fork 491
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
build: show all cython warnings #37885
base: develop
Are you sure you want to change the base?
Conversation
This change won't take effect for most people because the editable build (via |
Documentation preview for this PR (built with commit 4dbb878; changes) is ready! 🎉 |
What is going on here:
etc... |
Why can't The review question here is: what do you think about enabling all cython warnings as I suggest here? This adds a lot of cython warnings, but at least the |
|
Got to ask the author about that. |
The review question here is: what do you think about enabling all cython warnings as I suggest here? This adds a lot of cython warnings, but at least the Unraisable exception... warning seems a real problem (see #37792 (comment) -- after all of those are fixed maybe this warning should be turned into an error). |
"unraiseable" should definitely be turned on. warnings which are certainly bogus - better not. But OK, all on is good too. |
cebc320
to
4dbb878
Compare
I updated the PR so that all cython warnings are enabled, both in |
Thanks! I'll try it out and take a look. |
The output from all the warnings seems somewhat excessive. Perhaps here we should at least try to fix the warnings that come in from the most commonly included .pxd files |
Motivated by #37792 (comment), change cython configuration so we show all warnings.
This will lead to a number of warnings, but it's IMO better to know about that and works towards fixing as much warnings as possible (and we have a fair number of warnings that are indeed relevant and not just false positives).
📝 Checklist