Skip to content
This repository was archived by the owner on Aug 19, 2025. It is now read-only.
This repository was archived by the owner on Aug 19, 2025. It is now read-only.

SQLAlchemy 2.0 #530

Closed
Closed

Description

@immanelg

Will there be support for SQLAlchemy 2.0 or I should just use it directly?

Activity

  1. tarsil commented on Feb 28, 2023

    @tarsil
    Contributor

    @madkinsz Apologies as missed this one. So as far as I could understand, its not planned to give support to SQLA 2.0?

  2. Kludex commented on Feb 28, 2023

    @Kludex
    Contributor

    We need someone to maintain this package. 🤷

  3. Kludex commented on Feb 28, 2023

    @Kludex
    Contributor

    I'm not able to review a PR with that bump here...

    Any of you are? @rafalp @aminalaee

  4. rafalp commented on Feb 28, 2023

    @rafalp
    Contributor

    If PR's comes up that bumps SQLAlchemy support to 2.0, I'm fine with it. But I have no resources to develop one myself.

  5. tarsil commented on Feb 28, 2023

    @tarsil
    Contributor

    @rafalp @Kludex no worries. Give me a few days and I will have a look and open a PR with a possible integration with SQLA 2.0

    We are looking at possible backwards incompatible changes. Last time I tried a few things were changed internally within SQLA.

    I don't see a reason to have forks of this package just to add SQLA 2.0 when databases is already maintained

  6. Kludex commented on Feb 28, 2023

    @Kludex
    Contributor

    Cool. 👍

    Thanks. 🙏

  7. tarsil commented on Feb 28, 2023

    @tarsil
    Contributor

    No problem. I have products depending of databases and having the support for 2.0 we can leverage python 3. 2.0 does not support python 2 anymore.

  8. samuela commented on Jul 15, 2023

    @samuela

    any update on this issue? I'd really like to use slack-sdk which depends on databases but cannot due to this version constraint

  9. zanieb commented on Jul 15, 2023

    @zanieb
    Contributor

    @samuela there is #539 but it has unaddressed questions and could use another contributor

  10. samuela commented on Jul 15, 2023

    @samuela

    Thanks @zanieb ! I ended up finding a workaround for the time being

  11. added a commit that references this issue on Jul 15, 2023
  12. caarmen commented on Jul 15, 2023

    @caarmen

    @samuela Could you share some details of your workaround? 🙏🏻

  13. zanieb commented on Jul 15, 2023

    @zanieb
    Contributor

    @caarmen they removed the package entirely as seen in f9236b3

  14. ImEins commented on Sep 21, 2023

    @ImEins

    Can you guys tell us if you plan to add support for sqlalchemy 2.0 ?

  15. zanieb commented on Sep 25, 2023

    @zanieb
    Contributor

    @ImEins there is no maintainer that is going to implement it as this time. I will review a contribution adding support.

  16. Distortedlogic commented on Dec 8, 2023

    @Distortedlogic

    update?

  17. zanieb commented on Dec 8, 2023

    @zanieb
    Contributor

    The work at #539 is stalled as the author is busy with other things.

  18. tarsil commented on Feb 22, 2024

    @tarsil
    Contributor

    @ansipunk there is one PR opened yesterday that requires some attention. Hopefully today or tomorrow can be merged and we can perform a release.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    featureNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions