graphql-python / graphql-python/graphene
Is graphql-relay actually a requirement if relay is not going to be used?
- Dominant language
- Python
- Stars
- 8.2k
- Forks
- 818
- PR merge metrics
- No merged PRs in 30d
Description
I was hoping that `graphql-relay` could be removed as a base requirement in setup.py if it isn't actually required for people who have no need for relay.
Perhaps a specific install option like `pip install graphene[relay]` could be added for those that actually require it.
Obviously this would be a breaking change so it makes sense to do it before 3.0 is released if it will be done.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with setup.py and inspect how graphql-relay is declared and used by the package. Determine whether it can be moved to a relay-specific install option, then verify that a non-relay installation works and that relay users can still install the dependency; account for the proposed breaking change before 3.0.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100