Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BUG: Spyder/IPython (WinPython 10.2014) can't be started under WinXP #17

Closed
GHPS opened this issue Oct 22, 2014 · 2 comments

Comments

@GHPS
Copy link

@GHPS GHPS commented Oct 22, 2014

The problem: On my WinXP 32 machine I just tried to upgraded the WinPython 4.2014 installation to the brand new 10.2014 release. The previous version works fine, the current version doesn't hardly work - Spyder, IPythonQT and IPython Notebook doen't start no matter how hard I try to tweak the settings. The problem seem to be serious meaning that WinPython 10.2014 and even 8.2014 are unusable under XP.

At least IPythonQT Console gives a long traceback with an "OSError: [WinError 127]" (Procedure not found) at the end. This led my to the statement of an developer of the Zero MQ library (Christoph Gohlke) saying that the "Win 127" problem is not only known but expected in zmq and related to a missing DLL function in WinXP.
http://github.com/zeromq/pyzmq/issues/521

Seemingly I'm the last user of WinPython on XP on this planet...

The solution: Transplant the working zmq lib. I took the current WinPython-3.3.5 installation, deleted the contents of "python-3.3.5\Lib\site-packages\zmq" and replaced it with the files of the same directory from WinPython 4.2013. Everthing works a treat now...

P.S. Since the zmq lib is compiled against Python 3.3 you can't switch to WinPython 3.4 before the original problem is fixed (or someone provides a compiled version).
P.P.S. Seemingly Windows Server 2003 has the same problem
http://sourceforge.net/p/winpython/tickets/117/

@stonebig

This comment has been minimized.

Copy link
Contributor

@stonebig stonebig commented Oct 23, 2014

Thanks for the links, and the manual workaround !
You probably found the only workaround, as Winpython depends entirely on Christoph Gohlke binaries.

@sebix

This comment has been minimized.

Copy link
Contributor

@sebix sebix commented Oct 23, 2014

I will create a wiki page of your solution and link that somewhere. Supporting xp is not possible for us. Closed that for now.

@sebix sebix closed this Oct 23, 2014
@sebix sebix added wontfix bug feature-request and removed bug labels Oct 23, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.