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
pyzmq 26, Windows 11: Bad file descriptor #1981
Comments
Can I ask how you installed pyzmq and Python? Do you have any other Python versions available to test? Can you run a basic script like: import zmq
ctx = zmq.Context()
with ctx:
with ctx.socket(zmq.PUSH) as s:
s.bind("tcp://127.0.0.1:5555") |
same issue here. FYI @minrk, I've just run your code to confirm. import zmq
ctx = zmq.Context()
with ctx:
with ctx.socket(zmq.PUSH) as s:
s.bind("tcp://127.0.0.1:5555")
Also using python 3.12.3 via microsoft store(WIN 11) |
@minrk thanks for your patience, running the scripts you suggested results in: I installed python via Mirosoft store on windows 11. Python pip installed |
Interesting that you both got it via the Store. Do you have access to another source, e.g. a miniconda install or Python.org installer? Just to test if it's related to the Python installation instead of the environment? |
@minrk just confirmed that it does not happen with python.org release of 3.12.3, both on jupyter lab and the test code you provided. I've failed to test conda, since jupyter is only seems to be able to run in conda packages, not pip. I wanted to test in pyzmq >= 26.0.0 |
This is a pyzmq bug
What pyzmq version?
26.0.0
What libzmq version?
none
Python version (and how it was installed)
3.12.3
OS
windows 11
What happened?
When installing jupyter on a new windows machine, it will fail to connect to any python3 kernel, with the following error popup: "Error Starting KernelNetworkError when attempting to fetch resource."
To reproduce:
On a Powershell on a Windows 11 machine with python 3.12.3:
It works after I uninstall pyzmq and reinstall the Dec 5, 2023 version:
Code to reproduce bug
Traceback, if applicable
More info
No response
The text was updated successfully, but these errors were encountered: