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

TODO: SQLAlchemy 2.0 Support #2492

Open
ghost opened this issue Jul 14, 2023 · 0 comments
Open

TODO: SQLAlchemy 2.0 Support #2492

ghost opened this issue Jul 14, 2023 · 0 comments
Labels
Breaking Change Stuff that probably should be mentioned in a migration guide Feature Long-term Planning Things that need to happen at some point in the future, but need to NOT happen soon.

Comments

@ghost
Copy link

ghost commented Jul 14, 2023

Requested Feature

Currently Sopel depends on SQLA 1.4. That's already pretty good, as that brings us probably more than 90% of the way to being ready to convert to SQLA 2.0 (good job Exi! #2243).

This issue is being created mostly as a reminder to work on converting some bits of Sopel to work with SQLA 2.0 for Sopel 9 or some such. Exi might have more information to add in regards to this.

Problems Solved

If a user wants to write a plugin for Sopel, they can be sure they're using the latest and greatest SQLA. 😎

Alternatives

No response

Notes

Maintainers: feel free to edit the title and this issue text as desired. I know I'm not always the best with words.

@ghost ghost added Feature Needs Triage Issues that need to be reviewed and categorized labels Jul 14, 2023
@Exirel Exirel added Long-term Planning Things that need to happen at some point in the future, but need to NOT happen soon. Breaking Change Stuff that probably should be mentioned in a migration guide and removed Needs Triage Issues that need to be reviewed and categorized labels Jul 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Breaking Change Stuff that probably should be mentioned in a migration guide Feature Long-term Planning Things that need to happen at some point in the future, but need to NOT happen soon.
Projects
None yet
Development

No branches or pull requests

1 participant