TopGit tracks graphql-python/graphql-core-legacy on GitHub. The project has 371 stars. GraphQL base implementation for Python (legacy version – see graphql-core for the current one)
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
⚠️ This is the repository of GraphQL for Python 2 (legacy version).
The repository for the current version is available at
github.com/graphql-python/graphql-core.
This library is a port of GraphQL.js to Python
and up-to-date with release 0.6.0.
GraphQL-core 2 supports Python version 2.7, 3.5, 3.6, 3.7 and 3.8.
GraphQL.js is the JavaScript reference implementation for GraphQL,
a query language for APIs created by Facebook.
See also the GraphQL documentation at graphql.org and
graphql.org/graphql-js/graphql/.
For questions regarding GraphQL, ask Stack Overflow.
Getting Started
An overview of the GraphQL language is available in the
README for the
Specification for GraphQL.
The overview describes a simple set of GraphQL examples that exist as
tests
in this repository. A good way to get started is to walk through that README
and the corresponding tests in parallel.
Using GraphQL-core 2
Install from pip:
pip install "graphql-core<3"
GraphQL-core provides two important capabilities: building a type schema, and
serving queries against that type schema.
First, build a GraphQL type schema which maps to your code base.
This defines a simple schema with one type and one field, that resolves to a fixed value.
The resolver function can return a value, a promise, or an array of promises.
A more complex example is included in the top level
tests directory.
Then, serve the result of a query against that type schema.
query = '{ hello }'
result = graphql(schema, query)
# Prints
# {'hello': 'world'} (as OrderedDict)
print result.data
This runs a query fetching the one field defined. The graphql function will first ensure
the query is syntactically and semantically valid before executing it, reporting errors otherwise.
query = '{ boyhowdy }'
result = graphql(schema, query)
# Prints
# [GraphQLError('Cannot query field "boyhowdy" on type "RootQueryType".',)]
print result.errors
Executors
The graphql query is executed, by default, synchronously (using SyncExecutor). However the following executors are available if we want to resolve our fields in parallel:
graphql.execution.executors.asyncio.AsyncioExecutor: This executor executes the resolvers in the Python asyncio event loop.
graphql.execution.executors.gevent.GeventExecutor: This executor executes the resolvers in the Gevent event loop.
graphql.execution.executors.process.ProcessExecutor: This executor executes each resolver as a process.
graphql.execution.executors.thread.ThreadExecutor: This executor executes each resolver in a Thread.
graphql.execution.executors.sync.SyncExecutor: This executor executes each resolver synchronusly (default).
Usage
You can specify the executor to use via the executor keyword argument in the grapqhl.execution.execute function.
from graphql import parse
from graphql.execution import execute
from graphql.execution.executors.sync import SyncExecutor
ast = parse('{ hello }')
result = execute(schema, ast, executor=SyncExecutor())
print result.data
Contributing
After cloning this repo, create a virtualenv and ensure dependencies are installed by running:
Well-written tests and maintaining good test coverage is important to this project. While developing, run new and existing tests with:
pytest PATH/TO/MY/DIR/test_test.py # Single file
pytest PATH/TO/MY/DIR/ # All tests in directory
Add the -s flag if you have introduced breakpoints into the code for debugging.
Add the -v ("verbose") flag to get more detailed test output. For even more detailed output, use -vv.
Check out the pytest documentation for more options and test running controls.
GraphQL-core 2 supports several versions of Python. To make sure that changes do not break compatibility
with any of those versions, we use tox to create virtualenvs for each Python version and run tests with that version.
To run against all python versions defined in the tox.ini config file, just run:
tox
If you wish to run against a specific version defined in the tox.ini file:
tox -e py36
Tox can only use whatever versions of python are installed on your system. When you create a pull request, Travis will also be running the same tests and report the results, so there is no need for potential contributors to try to install every single version of python on their own system ahead of time. We appreciate opening issues and pull requests to make GraphQL-core even more stable & useful!
Is graphql-python/graphql-core-legacy open source?
Yes — graphql-python/graphql-core-legacy ships under the MIT license, which makes its source code freely readable (and, depending on license terms, forkable and reusable). Source: github.com/graphql-python/graphql-core-legacy.
What is graphql-python/graphql-core-legacy?
graphql-python/graphql-core-legacy (graphql-python/graphql-core-legacy) is a Python project on GitHub. From the project's own README: GraphQL base implementation for Python (legacy version – see graphql-core for the current one)
Where do I read more about graphql-python/graphql-core-legacy?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/graphql-python/graphql-core-legacy is the definitive source.
Read full README in the tab above.
Curious whether graphql-core-legacy is right for you?
Let ChatGPT, Claude, or Perplexity look into it — click below and see what AI actually says about graphql-core-legacy.