为何Windows平台的CPython未内置curses模块？与Linux存在差异的原因是什么？

Great question! Let’s break down this cross-platform discrepancy—it all ties back to the origins of the curses library and how Python handles platform-specific system dependencies.

• Curses is a Unix-native library
  The curses module in CPython is just a wrapper around the curses library, which has been a core part of Unix-like operating systems (including Linux, macOS, and BSD) for decades. These systems ship with the curses library preinstalled, so when CPython is compiled for Linux, it can directly link against this system-provided library and include the module in the standard distribution with zero extra work.

• Windows has a completely different terminal ecosystem
  Windows’ terminal infrastructure (going back to the original Command Prompt, and even modern tools like Windows Terminal) was built from scratch with a different model than Unix terminals. There’s no native curses library included with Windows—Microsoft historically used its own terminal control APIs (like the old conio.h for DOS/early Windows) which are incompatible with curses’ interface.

• Maintenance and priority tradeoffs
  The Python core team has limited resources to maintain cross-platform compatibility for every module. Porting curses to Windows would require building and maintaining a full compatibility layer to bridge the gap between Unix curses and Windows’ terminal APIs. Since there are solid third-party alternatives available for Windows users, this hasn’t been a high-priority addition to the standard library.

• A quick workaround for Windows
  If you need curses on Windows, you can install a third-party port via pip:

  pip install windows-curses
  

  This package provides a fully compatible implementation of the curses module tailored for Windows systems.

内容的提问来源于stack exchange，提问作者Martin Thoma