Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

State of defer in 3.3.0a3 and compatibility with latest spec

Open
#247 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
graphql, python

Research direction

No files or tests are named. Start by reviewing the defer implementation in the 3.3.0a3 code and comparing its behavior with the latest spec discussion; done would require confirming compatibility and stability for adopters.

Written by the indexing model from the issue text.

Description

Hi folks!

We use graphql-core, and we're looking to adopt defer. @Cito — could you comment on the stability of the defer implementation in 3.3.0a3? In particular, does it match what is in the latest spec?

3.3.0a3 was released on June 4th 2023, so perhaps it is quite stable, despite the alpha label.

Thank you!
–R

Dominant language
Python
Stars
531
Forks
147
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from graphql-python/graphql-core

All issues in graphql-python/graphql-core

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.