In SQLAlchemy 2.0, the previous standard way of interacting with the ORM, using the Query API has been made legacy as of 2.0+. It is, and will continue to be functional, but code should be updated. The LegacyAPIWarning is thrown in places where this is the case. The core changes for this new API have been in existence since version 1.4.
Looking at the major API changes section, version 1.4 made significant changes to the API to prepare to switch over to the Query API from 2.0 onwards, which is in use in the codebase.
SQLAlchemy 2.0 Migration Guide link for reference.
This is potentially the kind of task that would be good to try assigning to Copilot as I expect a good amount of the work to be mostly, or entirely simple code replacement.
In SQLAlchemy 2.0, the previous standard way of interacting with the ORM, using the Query API has been made legacy as of 2.0+. It is, and will continue to be functional, but code should be updated. The LegacyAPIWarning is thrown in places where this is the case. The core changes for this new API have been in existence since version 1.4.
Looking at the major API changes section, version 1.4 made significant changes to the API to prepare to switch over to the Query API from 2.0 onwards, which is in use in the codebase.
SQLAlchemy 2.0 Migration Guide link for reference.
This is potentially the kind of task that would be good to try assigning to Copilot as I expect a good amount of the work to be mostly, or entirely simple code replacement.