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

Quiver source

Open
#286 0 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

The issue names Quiver and the core-legacy backend but does not identify a repository file, test, or entry point. First verify whether Quiver can be open sourced and define the integration scope; done would require available Quiver source and an agreed backend implementation.

Written by the indexing model from the issue text.

Description

It seems like a lot of people (us included) will not be able to move off of core-legacy any time soon, and enjoy the fruits of native async/await. Given that Quiver seems dead, is there any chance that @syrusakbary will open source it so that we can include it as a backend and improve the performance of the core legacy library?

Dominant language
Python
Stars
371
Forks
175
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-legacy

All issues in graphql-python/graphql-core-legacy

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.