Skip to content

Sqlalchemy 2 support for CI #2

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

Closed
wants to merge 21 commits into from
Closed

Conversation

phillipuniverse
Copy link

Opening this so I can run my own GH actions to make sure they succeed instead of waiting for approval in the parent repo.

javimudi and others added 21 commits January 9, 2024 09:30
Under some circunstances, such as prepping an aliased subquery to be joined later on, the model entity is missing,
provoking an error when trying to apply filters.

(cherry picked from commit edc7c24)
This property is removed in SQLAlchemy 2.x
… .gitignore

This allows Tox to find all Python versions when using pyenv
drop_all() makes the 'bind' positional argument required
Specify compatible versions of SQLAlchemy and SQLAlchemy-Utils for Python, SQLAlchemy versions
Simplifies tox expressions and doesn't change anything fundamental about this library. 0.38.3 dropped support for Python 3.4 and 3.5 which sqlalchemy-filters never supported in the first place
@phillipuniverse
Copy link
Author

CI back to working in the upstream.

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

Successfully merging this pull request may close these issues.

3 participants