TODO: SQLAlchemy 2.0 Support #2492
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.
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 SQLA2.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.
The text was updated successfully, but these errors were encountered: