Breaking change in graphql-core
See original GitHub issueThere’s some backward-compatibility breaks in graphql-core==3.0.0
, that lead to the following import error:
from gql import Client
ImportError Traceback (most recent call last)
<ipython-input-1-2d34726b19bf> in <module>
----> 1 from gql import Client
~\AppData\Local\Continuum\miniconda3\lib\site-packages\gql\__init__.py in <module>
1 from .gql import gql
----> 2 from .client import Client
3
4 __all__ = ['gql', 'Client']
~\AppData\Local\Continuum\miniconda3\lib\site-packages\gql\client.py in <module>
1 import logging
2
----> 3 from graphql import parse, introspection_query, build_ast_schema, build_client_schema
4 from graphql.validation import validate
5
ImportError: cannot import name 'introspection_query' from 'graphql' (C:\Users\nathan.demaria\AppData\Local\Continuum\miniconda3\lib\site-packages\graphql\__init__.py)
AFAIK the solution here is add a ceiling graphql-core<3.0.0
to the install_requires
of this package, but I’m curious if somebody familiar with the plan for packages in this repo has better options/longer term recommendations - I see repos for graphql-core-next
and gql-next
, and it looks like the graphql-core
package is now published to PyPI from the -next
repo, but gql
is still from this repo.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Breaking changes - GitHub Docs
Breaking changes are any changes that might require action from our integrators. We divide these changes into two categories: Breaking: Changes that will...
Read more >Breaking Changes in GraphQL with Zero Downtime
One of the core promises of GraphQL is that you can build an API without versioning or breaking changes. Breaking changes occur when...
Read more >Versioning fields in GraphQL - LogRocket Blog
Breaking changes are those that remove a type, field, or directive, or modify the signature of an already existing field (or directive), such...
Read more >graphql-core Changelog - pyup.io
Patch release GraphQL-core v3.1.7, based on GraphQL.js v15.8.0. This release includes minor changes and improvements, in particular: - Set enum value values to ......
Read more >GraphQL Best Practices
Why do most APIs version? When there's limited control over the data that's returned from an API endpoint, any change can be considered...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks @Cito!
@syrusakbary Can you help push out the patch release to PyPI?
Version 0.2.0 with this fix has now been released on PyPI.