Closed jgehrcke closed 10 months ago
I think by pinning greenlet==2.0.2 this seems to fix the gevent problems for now as we can upgrade to gevent==23.9.0.post1. Perhaps its worth doing a point release and then another one once this whole gevent bug issue is resolved?
Greenlet 3.0.1 was released on Oct 25. On macos 11 with Python 3.8 and 3.9 (edit: and also all other tested versions up to 3.12) this results in a segfault in gipc's test suite, e.g.:
This seems related to https://github.com/python-greenlet/greenlet/issues/382.
Looking for now into pinning greenlet to 2.0.2 for Python versions smaller than 3.12.
Edit:
Not the right solution. It's the specific binary build of 3.0.1 for darwin which is broken currently on PyPI. Temporary workaround is to switch in CI to use source builds. That will leave users affected until a new binary wheel is published by greenlet maintainers (helloooo Jason :-)).