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

[MAINT] - sqlalchemy 2.0 migration #931

Open
peytondmurray opened this issue Oct 28, 2024 · 0 comments · May be fixed by #970
Open

[MAINT] - sqlalchemy 2.0 migration #931

peytondmurray opened this issue Oct 28, 2024 · 0 comments · May be fixed by #970
Assignees
Labels
needs: investigation 🔎 Someone in the team needs to look into this issue before scoping

Comments

@peytondmurray
Copy link
Contributor

Context

sqlalchemy==2.0 has been out since January 2023. This issue is to track work on an upgrade path before support for <2.0 is dropped.

Value and/or benefit

sqlalchemy<2.0 is still seeing releases, but at some point legacy support will be dropped. It would be nice to get ahead of this so that we're not caught off guard by it when it gets announced.

Anything else?

No response

@peytondmurray peytondmurray added needs: investigation 🔎 Someone in the team needs to look into this issue before scoping needs: triaging 🚦 Someone needs to have a look at this issue and triage labels Oct 28, 2024
@soapy1 soapy1 moved this from New 🚦 to TODO 📬 in conda-store 🐍 Nov 7, 2024
@soapy1 soapy1 self-assigned this Nov 8, 2024
@soapy1 soapy1 removed the needs: triaging 🚦 Someone needs to have a look at this issue and triage label Nov 8, 2024
@soapy1 soapy1 moved this from TODO 📬 to In Progress 🏗 in conda-store 🐍 Nov 8, 2024
@soapy1 soapy1 linked a pull request Nov 8, 2024 that will close this issue
3 tasks
@soapy1 soapy1 moved this from In Progress 🏗 to In review 👀 in conda-store 🐍 Nov 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs: investigation 🔎 Someone in the team needs to look into this issue before scoping
Projects
Status: In review 👀
Development

Successfully merging a pull request may close this issue.

2 participants