>> If not, I'd like to propose that we phase out that support: the Windows >> 2.7 installer should display a warning; 3.2 will stop supporting Windows >> 2000. > > Is there any reason for this? I can understand dropping Windows 9x > due to the lack of Unicode support but is there anything missing from > Windows 2000 that makes supporting it difficult? See http://bugs.python.org/issue6926 The SDK currently hides symbolic constants from us that people are asking for. In addition, we could simplify the code in dl_nt.c around GetCurrentActCtx and friends, by linking to these functions directly. Regards, Martni
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4