Armin Rigo <[email protected]> added the comment: No, it seems to be simply compiling with cpyext the "win32api" module. As we are low on people with Windows machines, we can't test all the Windows-only extension modules, even though I agree that "win32api" seems central. I don't know it well enough to know what the best path forward would be: either hack it to not call these three functions; or add support for the three functions in pypy/module/cpyext/, either as stubs or as a real implementation; or reimplement win32api or a part of it by rewriting it as a cffi module (which looks like a big job, even if it also looks like all APIs should be very easy to map).
---------- nosy: +arigo ________________________________________ PyPy bug tracker <[email protected]> <https://bugs.pypy.org/issue1720> ________________________________________ _______________________________________________ pypy-issue mailing list [email protected] https://mail.python.org/mailman/listinfo/pypy-issue
