[issue31951] import curses is broken on windows

Change by Serhiy Storchaka : -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> curses for win32 ___ Python tracker ___ ___

[issue31951] import curses is broken on windows

joe m added the comment: I would much prefer the curses module to be supported in newer versions since I believe that curses is installed as a built in module (not sure about that). Anyhow, thank you for your help but I have found a replacement module called "asciimatics" which for fills all

[issue31951] import curses is broken on windows

Serhiy Storchaka added the comment: There are two open issues for adding support of the curses module on Windows: issue1005895 and issue2889. -- nosy: +serhiy.storchaka ___ Python tracker ___

[issue31951] import curses is broken on windows

Zachary Ware added the comment: Curses is available for Windows from Christopher Gohlke's site: https://www.lfd.uci.edu/~gohlke/pythonlibs/#curses We should clean up this situation, though, either by making the state of Windows curses support explicit in the docs or by actually adding support

[issue31951] import curses is broken on windows

Paul Moore added the comment: The docs for the curses module say "While curses is most widely used in the Unix environment, versions are available for Windows, DOS, and possibly other systems as well." This is the only mention of platform support I can see. It might be worth making the platfo

[issue31951] import curses is broken on windows

STINNER Victor added the comment: The curses module is not supported on Windows. -- nosy: +haypo ___ Python tracker ___ ___ Python-b

[issue31951] import curses is broken on windows

New submission from joe m : Importing curses on Windows install calls the following: Traceback (most recent call last): File "", line 1, in File "C:\Users\user name\AppData\Local\Programs\Python\Python36-32\lib\curses\__init__.py", line 13, in from _curses import * ModuleNotFoundErro