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

`graphql.utilities.print_schema` module contents are hidden behind `utilities` package

Open
#209 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
graphql, python
Domain
api

Research direction

Start by reproducing the import behavior described in the issue, then inspect src/graphql/utilities/init.py and src/graphql/utilities/print_schema.py, including the latter's ALL. Done means the public import exposes the intended print_schema module contents without losing the documented behavior of the existing utility function.

Written by the indexing model from the issue text.

Description

Summary

graphql.utilities.__init__.py's export of print_schema function shadows the module of graphql.utilities.print_schema

https://github.com/graphql-python/graphql-core/blob/0c93b8452eed38d4f800c7e71cf6f3f3758cd1c6/src/graphql/utilities/__init__.py#L28-L31

So assume this:

from graphql.utilities import print_schema

Expected behavior

The module graphql.utilities.print_schema.

Results

As of v3.3.0a3

The function graphql.utilities.print_schema.print_schema() the function.

Discussion

https://github.com/graphql-python/graphql-core/blob/v3.3.0a3/src/graphql/utilities/print_schema.py#L32 does use a __ALL__, but its contents, which are typed, aren't exported.

Our use case

In earlier graphql-core versions, we would patch print_object - and during migration to graphql-core we found that wasn't available due to package structure.

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.