-
-
Notifications
You must be signed in to change notification settings - Fork 29.4k
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
curses for win32 #40725
Comments
I have paths for compile _curses module. |
Logged In: YES In the cursesmodule patch, the first argument to intrflush use_env() is apparently a no-op for PDcurses; why not just In the setting of _C_API_VERSION, what does the string Except for the above questions, the patches to |
Logged In: YES
|
Logged In: YES
Andrew, Sorry, but I'm confused. What exactly are you Thanks, |
Logged In: YES As maintainer of the curses module, applying the patch is OK (Note that the patch to test_curses.py won't apply cleanly; |
Logged In: YES If the patch affects Cygwin, then it's not obvious: $ fgrep -i cygwin _cursesmodule.c.patch mingw32.mak
test_curses.py.patch
$ However, it seems to affect the native Windows build: $ grep -i 'platform.*win' _cursesmodule.c.patch mingw32.mak
test_curses.py.patch
test_curses.py.patch:+ if sys.platform == 'win32': Please point out actually where the patch affects Cygwin. |
Logged In: YES Ah; I looked at the initial description which says 'mingw32' |
Logged In: YES AFAICT, this patch applies to the standard Windows build. |
Can this be considered a duplicate of bpo-2889? |
Sorry, but I don't know. I haven't looked at this issue for almost five years! And when I did, I only looked as far to determine it wasn't Cygwin related. |
Brian or Tim any interest in this? I consider bpo-2889 to be a duplicate of this and not the other way around. |
I have zero knowledge and experience when it comes to curses so I'm afraid I can't really provide much here. One thing I can say is that this patch would have to be converted to be compiled by MSVC rather than MinGW. That was an early issue with bpo-2889 but it appears that patch was converted. |
It looks as though bpo-2889 has a better chance of getting into the VS build than this one, which appears to be MingW-based (at a quick glance). I'm loosely keen to see it in, although I have no knowledge of curses as such. I'll assign it to myself so it appears on my to-do queue but I'm not promising to do anything with it immediately. Anyone who feels up to the task, feel free to take it off me. Mark: why do you consider bpo-1005895 the master, so to speak? I can see more mileage in pursuing the other? |
Tim: mainly because this was raised some 4 years earlier and the title of bpo-2889 "curses for windows (alternative patch)" |
Is this worth pursuing as https://docs.python.org/3/howto/curses.html states "The Windows version of Python doesn’t include the curses module. A ported version called UniCurses is available" ? This is available at https://pypi.python.org/pypi/UniCurses |
Well, basically any solution is better than nothing ;) |
See also #47138 |
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: