[issue32287] Import of _pyio module failed on cygwin

2018-03-23 Thread Berker Peksag
Change by Berker Peksag : -- superseder: -> _pyio module broken on Cygwin / setmode not usable ___ Python tracker ___

[issue32287] Import of _pyio module failed on cygwin

2017-12-19 Thread Erik Bray
Erik Bray added the comment: Indeed, this is a duplicate of #28459. I'll also update the existing patch to a pull request. -- resolution: -> duplicate stage: needs patch -> resolved status: open -> closed ___ Python tracker

[issue32287] Import of _pyio module failed on cygwin

2017-12-12 Thread Masayuki Yamamoto
Masayuki Yamamoto added the comment: This issue seems to duplicate #28459. #28459 has a patch (implement _setmode() by ctypes on _pyio). I'm not sure _setmode() will be used in other places in the future, but the patch just works at the moment. In addition, I have

[issue32287] Import of _pyio module failed on cygwin

2017-12-12 Thread Zachary Ware
Zachary Ware added the comment: Right, so you should raise an issue with cherrypy :). You're more likely to get a fix from them quickly, and their usage of _pyio is not correct anyway. Also, note that Cygwin is not (anymore/yet) a fully-supported platform. We're

[issue32287] Import of _pyio module failed on cygwin

2017-12-12 Thread Christian Heimes
Christian Heimes added the comment: Could you please file a bug with cherrypy and get it fixed? Cygwin not yet officially supported and stable. Erik is working hard on stable support for 3.7. -- ___ Python tracker

[issue32287] Import of _pyio module failed on cygwin

2017-12-12 Thread Matúš Valo
Matúš Valo added the comment: I am using not using _pyio module directly but I am using cherrypy server which is using this module (more precisely its component cheroot):

[issue32287] Import of _pyio module failed on cygwin

2017-12-12 Thread Zachary Ware
Zachary Ware added the comment: Presumably this issue does prevent us from testing _pyio on Cygwin, which is not ideal. The outside usage of _pyio is definitely not supported, as Christian said, but this may be worth fixing anyway. -- nosy: +masamoto,

[issue32287] Import of _pyio module failed on cygwin

2017-12-12 Thread R. David Murray
Change by R. David Murray : -- nosy: +erik.bray ___ Python tracker ___ ___

[issue32287] Import of _pyio module failed on cygwin

2017-12-12 Thread Christian Heimes
Christian Heimes added the comment: The msvcrt module is part of the standard library on Windows. Your cygwin installation may be incomplete. By the way, why are you importing a private module? _pyio isn't a public API and shouldn't be used. -- nosy:

[issue32287] Import of _pyio module failed on cygwin

2017-12-12 Thread Matúš valo
Matúš valo added the comment: Previous import is working in python 2.7: $ python Python 2.7.14 (default, Oct 31 2017, 21:12:13) [GCC 6.4.0] on cygwin Type "help", "copyright", "credits" or "license" for more information. >>> import _pyio >>> --

[issue32287] Import of _pyio module failed on cygwin

2017-12-12 Thread Matúš valo
New submission from Matúš valo : When trying to impor _pyio from python3 in Cygwin, import fails with exception: $ python3 Python 3.6.3 (default, Oct 31 2017, 19:00:36) [GCC 6.4.0] on cygwin Type "help", "copyright", "credits" or "license" for more information. >>> import