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

[DNM][deprecation] deprecate non asyncio hubs #945

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

4383
Copy link
Member

@4383 4383 commented Mar 25, 2024

In accordance with our recent maintenance goals we sets [1][2] and in accordance with the recent addition of the asyncio hub [3], this patch proposes to deprecate all the other existing hubs, the non asyncio hubs, to encourage users to start their migration to asyncio.

[1] #835
[2] #824
[3] #868

In accordance with our recent maintenance goals we sets [1][2] and in
accordance with the recent addition of the asyncio hub [3], this patch
proposes to deprecate all the other existing hubs, the non asyncio hubs,
to encourage users to start their migration to asyncio.

[1] eventlet#835
[2] eventlet#824
[3] eventlet#868
Copy link

codecov bot commented Mar 25, 2024

Codecov Report

Attention: Patch coverage is 90.00000% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 56%. Comparing base (e1afe7b) to head (32efe15).

Files Patch % Lines
eventlet/hubs/kqueue.py 50% 1 Missing ⚠️
Additional details and impacted files
@@          Coverage Diff          @@
##           master   #945   +/-   ##
=====================================
  Coverage      56%    56%           
=====================================
  Files          89     89           
  Lines        9766   9776   +10     
  Branches     1818   1818           
=====================================
+ Hits         5475   5484    +9     
- Misses       3920   3921    +1     
  Partials      371    371           
Flag Coverage Δ
ipv6 23% <70%> (+<1%) ⬆️
py310asyncio 52% <70%> (+<1%) ⬆️
py310epolls 53% <90%> (+<1%) ⬆️
py310poll 53% <80%> (+<1%) ⬆️
py310selects 53% <70%> (+<1%) ⬆️
py311asyncio 53% <70%> (+<1%) ⬆️
py311epolls 53% <90%> (-1%) ⬇️
py312asyncio 50% <70%> (+<1%) ⬆️
py312epolls 51% <90%> (+<1%) ⬆️
py37asyncio 50% <70%> (+<1%) ⬆️
py37epolls 51% <90%> (+<1%) ⬆️
py38asyncio 51% <70%> (+<1%) ⬆️
py38epolls 53% <90%> (+<1%) ⬆️
py38openssl 51% <90%> (+<1%) ⬆️
py38poll 53% <80%> (+<1%) ⬆️
py38selects 53% <70%> (+<1%) ⬆️
py39asyncio 51% <70%> (+<1%) ⬆️
py39dnspython1 51% <90%> (+<1%) ⬆️
py39epolls 53% <90%> (+<1%) ⬆️
py39poll 53% <80%> (+<1%) ⬆️
py39selects 53% <70%> (+<1%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@itamarst
Copy link
Contributor

My concern is whether we think the asyncio hub is actually in working condition, since we've just fixed a bunch of major bugs in it.

@4383
Copy link
Member Author

4383 commented Mar 27, 2024

I was thinking to propose to holds this PR. Maybe we can hold it until as long as the work on the devstack integration is not completed.

https://review.opendev.org/c/openstack/devstack/+/914108

We'll see more clearly once this work is finished.

@4383 4383 changed the title [deprecation] deprecate non asyncio hubs [DNM][deprecation] deprecate non asyncio hubs Mar 27, 2024
@4383
Copy link
Member Author

4383 commented Mar 27, 2024

Updated the title with "do not merge".

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

Successfully merging this pull request may close these issues.

None yet

2 participants