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
_cursesmodule compile error in OS X 32-bit-only installer build #58433
Comments
./Modules/_cursesmodule.c:279: error: syntax error before 'cchar_t' Note to self, this installer build builds its own version of ncurses. It may need adjusting for 3.3. |
Is this issue still valid? |
It was still valid as of 3.3.0a4. |
And will you fix it for beta1, or do you think it can be done later? BTW, what is the syntax error here? I don't really see it... |
New changeset 2035c5ad4239 by Ned Deily in branch 'default': |
It turns out that the Unicode support for curses did not build correctly on OS X at all. There were two issues:
|
Cool, thanks for the fix! |
P.S. All is not perfect. I initially missed re-running test_curses with the system ncurses library on OS X where ncurses is at 5.4 or with the 32-bit-installer which builds ncurses 5.5. When I did, test_curses failed as described in bpo-15037. test_curses passes when Python is built with a MacPorts ncurses 5.9. The best solution would be to update the installer builds to build and use the latest ncurses 5.9. That may have to wait until after 3.3.0b1. |
P.P.S. I've updated the OS X installers as of 3.3.0b2 to build and link with a local copy of ncurses 5.9 rather than older Apple-supplied ones. test_curses now passes. |
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: