Skip to content

Conversation

philpep
Copy link

@philpep philpep commented Dec 6, 2022

Require SQLAlchemy>=1.4 and follow recommended migration path for future SQLAlchemy 2.0: https://docs.sqlalchemy.org/en/14/changelog/migration_20.html

Turn SQLALCHEMY_WARN_20=1 in tests and set PYTHONWARNINGS to always::DeprecationWarning so we get DeprecationWarning displayed during tests.

Fix some contruction which are no longer compatible with SQLAlchemy 2:

  • import declarative_base from sqlalchemy.orm
  • Use table.update().where(...) instead of table.update(...)
  • Use table.delete().where(...) instead of table.delete(...)
  • Drop use of legacy select() with a list argument
  • Drop use of legacy case() with a list argument
  • Use session.get(Model, pk) instead of session.query(Model).get(pk)

Require SQLAlchemy>=1.4 and follow recommended migration path for future SQLAlchemy 2.0: https://docs.sqlalchemy.org/en/14/changelog/migration_20.html

Turn SQLALCHEMY_WARN_20=1 in tests and set PYTHONWARNINGS to
always::DeprecationWarning so we get DeprecationWarning displayed in
during tests.

Fix some contruction which are no longer compatible with SQLAlchemy 2:

* import declarative_base from sqlalchemy.orm
* Use table.update().where(...) instead of table.update(...)
* Use table.delete().where(...) instead of table.delete(...)
* Drop use of legacy select() with a list argument
* Drop use of legacy case() with a list argument
* Use session.get(Model, pk) instead of session.query(Model).get(pk)
@MeRuslan
Copy link

hello, is this going anywhere?

@corentinclichy
Copy link

Do you know if you will be able to merged soon ?

@evgenybf
Copy link

@fayazkhan
Copy link
Collaborator

Hi, what earlier versions of SQLA would this change support?

@fayazkhan
Copy link
Collaborator

#104 will probably duplicate some of this effort. Main difference is that I'll be trying to support lower versions as well.

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.

5 participants