Skip to content

CASSPYTHON-13: Remove eventlet, gevent and twisted event loops#1293

Open
brettabamonte wants to merge 2 commits into
apache:trunkfrom
brettabamonte:CASSPYTHON-13
Open

CASSPYTHON-13: Remove eventlet, gevent and twisted event loops#1293
brettabamonte wants to merge 2 commits into
apache:trunkfrom
brettabamonte:CASSPYTHON-13

Conversation

@brettabamonte
Copy link
Copy Markdown

Drops support for the eventlet, gevent, and twisted event loops.

Went through:

  • Event loop code
  • Documentation
  • Testing/CI infrastructure

By dropping these three event loops I don't see why clients would use pyOpenSSL. As a result I dropped all lingering support for it in cassandra/datastax/insights/reporter.py.

Addresses: https://issues.apache.org/jira/browse/CASSPYTHON-13

Testing:

  • Unit tests passed on Python versions 3.10-3.14

@absurdfarce
Copy link
Copy Markdown
Contributor

Thanks for the PR @brettabamonte!

CASSPYTHON-13 is currently aimed at 3.31.0, which is our next minor version bump. We're currently working on getting 3.30.1 out the door; we're close but (as always) it's the details that bog ya down. I mention all of this to say that I'll probably hold off on merging this until 3.30.1 has actually been released. I don't want to merge something aimed at a future release until we know we're good with the current one... otherwise you wind up in the land of reverts, and nobody wants to be there. :)

As soon as 3.30.1 is out we'll be shifting to 3.31.0 pretty quickly... and this removal is definitely a significant part of what we're planning for 3.31.0.

Thanks again!

@brettabamonte
Copy link
Copy Markdown
Author

Thanks for the PR @brettabamonte!

CASSPYTHON-13 is currently aimed at 3.31.0, which is our next minor version bump. We're currently working on getting 3.30.1 out the door; we're close but (as always) it's the details that bog ya down. I mention all of this to say that I'll probably hold off on merging this until 3.30.1 has actually been released. I don't want to merge something aimed at a future release until we know we're good with the current one... otherwise you wind up in the land of reverts, and nobody wants to be there. :)

As soon as 3.30.1 is out we'll be shifting to 3.31.0 pretty quickly... and this removal is definitely a significant part of what we're planning for 3.31.0.

Thanks again!

Thanks for the heads up @absurdfarce. Is there anything for the 3.30.1 release that could use an extra set of hands? Happy to help get more involved in the project.

If not, are there any items from the TODO list that should get focus for 3.31.0?

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants