graphene-sqlalchemy depends on outdated graphql-core version.

[rohinb2]

Hi, I have been using graphene-sqlalchemy in my project for a while now.

However, due to this bug, I need to update to the latest version of gql, which depends on graphql-core >= 3.1. However, this package depends on an older version of graphql-core:

ERROR: Cannot install graphene-sqlalchemy and graphql-core==3.1.5 because these package versions have conflicting dependencies.
#16 5.660
#16 5.660 The conflict is caused by:
#16 5.660     The user requested graphql-core==3.1.5
#16 5.660     graphene 2.1.9 depends on graphql-core<3 and >=2.1
#16 5.660     The user requested graphql-core==3.1.5
#16 5.660     graphene 2.1.8 depends on graphql-core<3 and >=2.1
#16 5.660     The user requested graphql-core==3.1.5
#16 5.660     graphene 2.1.7 depends on graphql-core<3 and >=2.1
#16 5.660     The user requested graphql-core==3.1.5
#16 5.660     graphene 2.1.6 depends on graphql-core<3 and >=2.1
#16 5.660     The user requested graphql-core==3.1.5
#16 5.660     graphene 2.1.5 depends on graphql-core<3 and >=2.1
#16 5.660     The user requested graphql-core==3.1.5
#16 5.660     graphene 2.1.3 depends on graphql-core<3 and >=2.1
#16 5.660
#16 5.660 To fix this you could try to:
#16 5.660 1. loosen the range of package versions you've specified
#16 5.660 2. remove package versions to allow pip attempt to solve the dependency conflict
#16 5.660
#16 5.660 ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/user_guide/#fixing-conflicting-dependencies

Are there plans to release a new version that is compatible with the latest versions of these libraries? Thanks for the help!

[richin13]

This sould be solved with a new release being pushed to pypi. A temporary solution for you could be to use the beta release (pip install 'graphene-sqlalchemy==3.0.0b1') while #323 gets merged and a new stable release gets published on PyPI.

@mvanlonden can you take a look at #323 and publish a new version in PyPI? 🙏🏼

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related topics referencing this issue.