Steve Dower added the comment: I've been ignoring this because I wasn't assigned...
Here's the options. If we make it load ucrtbase.dll directly (which does still have named exports, and also uses the API schema on Windows 10): * some code that uses it will need updating (due to API changes since VC9/VC10) * code may need to change depending on OS updated (which could change the ucrtbase exports) * much existing code using this will probably work If we leave it as is: * all existing uses will obviously fail, nothing subtle * users will either substitute the name themselves, find an equivalent stdlib function, or use a supported Windows API Having just written that out, I still think not supporting it is best, but I do need to write it up in the porting info still. Any other thoughts? ---------- assignee: -> steve.dower _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue23606> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
