Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Upgrade strawberry-graphql version
See original GitHub issueDescription
The current requirement strawberry-graphql~=0.93.14 pins graphql-core = "~3.1.0" (https://github.com/strawberry-graphql/strawberry/blob/b69473a082665b08a9be1e246f317ca9cb6ea964/pyproject.toml#L38) which conflicts with gql 's requirement of graphql-core>=3.2,<3.3 (https://github.com/graphql-python/gql/blob/master/setup.py#L6)
Context
Any kedro project utilizing gql will have a difficult time also using kedro-viz
Possible Implementation
Is it possible to bump up kedro-viz 's requirement for strawberry-graphql ? Or make it more flexible?
Checklist
- Include labels so that we can categorise your feature request
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
My inclination is also to use
>=0.93.14,<1.0or similar and let the environment solver figure things out. But I’ll be honest, I haven’t spent time looking at the related deps.@AntonyMilneQB IIRC most of the problems with strawberry have seen are mypy-related, so I think it’s safe to relax the dependency and maybe be a bit less strict about mypy next time it blows up for strawberry.
Re dependabots, it’s similar to the CI config situation … I just never got to it 😦 I’m sorry.