-
-
Notifications
You must be signed in to change notification settings - Fork 18k
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
Error on Warnings From C Extensions #30609
Comments
+1 in this in at least linux to start |
the algos.c ones are a result of needing to filter out invalid pairs of dtypes from fused types. The aggregations.pyx one should be straightforward. |
PRs welcome to address any part of these @jbrockmendel
…Sent from my iPhone
On Jan 1, 2020, at 9:22 PM, jbrockmendel ***@***.***> wrote:
the algos.c ones are a result of needing to filter out invalid pairs of dtypes from fused types.
The aggregations.pyx one should be straightforward.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
@WillAyd I can't build master on OSX with py38 bc of tp_print warnings and "Werror". Can you? |
Haven’t set up a 38 env yet - can you post the warnings?
…Sent from my iPhone
On Mar 27, 2020, at 6:13 PM, jbrockmendel ***@***.***> wrote:
@WillAyd I can't build master on OSX with py38 bc of tp_print warnings and "Werror". Can you?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
They end with:
|
Can you look at the C file and see the Cython code that generates the line throwing the warning? |
@jbrockmendel can you confirm downgrading Cython to 0.29.13 fixes the issue? From what I can tell this started back with a fix in Cython 0.29.10 cython/cython#2976 which worked around an issue with the Py38 beta https://bugs.python.org/issue37250 Interestingly enough I noticed a change in Cython 0.29.14 that reintroduced code paths touching When trying locally things work in Cython 0.29.13 for me but not in 0.29.14 . If you can confirm as well can open an issue on the Cython side of things |
Yes, downgrading to cython 0.29.13 allowed me to compile on 3.8 |
@jbrockmendel can you also try Cython 3.0? Worked for me as well; maybe easiest to just skip the specific combo of Cython 0.29.14 with Python 3.8 on macOS... |
closing this issue since this was actually completed; but looks like a few issues springing up after this. I think will be easier to track in #30609 |
@WillAyd do you still need me to do this? |
No hold off for now
On Apr 2, 2020, at 11:27 AM, jbrockmendel ***@***.***> wrote:
can you also try Cython 3.0?
@WillAyd <https://github.com/WillAyd> do you still need me to do this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#30609 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEU4UI2WW5TJN4LI5VMYU3RKTKKNANCNFSM4KB5ODEA>.
William Ayd
william.ayd@icloud.com
|
May differ on other platforms, but currently I see about 19 warnings from C extensions still left. I think we should aim to clean these up and set the
Werror
flag in CI as can help be proactive in identifying bugs from extensionsHere is the list of remaining warnings from a parallel build, so order may not be relevant
The text was updated successfully, but these errors were encountered: