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

Update to greenlet 2.0 #1922

Merged
merged 13 commits into from Oct 31, 2022
Merged

Update to greenlet 2.0 #1922

merged 13 commits into from Oct 31, 2022

Conversation

jamadden
Copy link
Member

Fixes #1909

Before releasing this, we'll need a greenlet 2.0 final, and to take the 'rcX' qualifiers out of our dependency declarations (since those are sticky).

Fixes #1909

We'll need to release a final greenlet 2.0 and remove the rc qualifiers here before releasing gevent, because pre-release qualifiers are contagious.
Its failing in a weird way that doesn't happen locally.

There is a remaining issue, which lies somewhere in greenlet, seen in
test__monkey_hub_in_thread and test__threading_monkey_in_thread:

  Fatal Python error: Python memory allocator called without holding the GIL

  Python runtime state: finalizing (tstate=0xd5f3e0)

  Thread 0x00007f511f66b700 (most recent call first):
  <no Python frame>

Obviously this mixes with threads. greenlet uses Py_AddPendingCall to
move some work to other threads, but apparently something is still
happening at the wrong time.
Request this for the two IDNA cases, which somehow give different errors using the same resolver on GHA.
@arcivanov
Copy link
Contributor

FYI, Python 3.11 has been released. These tests are still against 3.11.0-rc.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants