Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[Bug]: Python files can disappear from the graph when a class is used before it's defined

Cerrado
  • ¿Algo no está bien?
#4,334 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

  • #4343 de @Mpasha17 — cerrado sin fusionar

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
72/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
python
Área
devtools

Línea de trabajo

Start by running graphify update . on the two-file reproduction in the issue and inspect graphify-out/graph.json to trace how the class reference before its definition affects file and class nodes. Find the Python parsing and graph construction entry points that handle those references; the issue does not name specific source files or tests. Done means widget.py remains in the graph, references resolve to its Widget class, and the missing call from Helper.make appears.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

What's happening

In some Python projects, whole files go missing from the graph, and the classes inside them get tangled up. There's no error, so it's easy to miss.

I noticed it on rich: when I ran graphify update rich/rich, two of its main files, markdown.py and syntax.py, weren't in the graph at all.

When it happens:

  • the file itself disappears from the graph
  • the class with the same name as the file ends up "containing" itself and every other class in the file
  • other files that import it look like they import the class instead of the file
  • some calls made from inside that file are quietly left out

When it happens

All three of these at once:

  1. The file is directly in the folder you point graphify at, not in a subfolder
  2. It has a class with the same name as the file, like Widget in widget.py
  3. Something earlier in that file mentions the class before it's defined, like a type hint w: Widget

Naming a file after its main class is pretty common, like console.py with Console, so this shows up in real projects.

How to see it for yourself

Make a folder with these two files and run graphify update .:

widget.py

from __future__ import annotations

class Helper:
    def make(self, w: Widget) -> None:
        w.draw()

class Widget:
    def draw(self):
        return 1

app.py

from widget import Widget

def use(w: Widget):
    w.draw()

Then look at graphify-out/graph.json:

  • there's no widget.py node
  • Widget "contains" itself and Helper
  • app.py imports Widget the class instead of widget.py the file
  • the call from Helper.make to Widget.draw is missing, while the same call from app.py is there

What should happen

widget.py should be in the graph like any other file, and the Widget it mentions should just point to the class defined lower down in the same file.

How much it matters

I checked graphify's call links against Jedi on rich. On 0.9.85, with this fixed, graphify finds 54 more correct calls, going from 64.6% to 68.6%, with no wrong links added and none lost. Both missing files come back too.

Version: graphify 0.9.85 · macOS 26.4 · Python 3.14

Lenguaje dominante
Python
Estrellas
124k
Forks
11.9k
Sin PR fusionados en 30 d

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Graphify-Labs/graphify

Todos los issues de Graphify-Labs/graphify

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.