Fine-grained: failure to propagate change to module alias

Open
#4,532 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
devtools

Research direction

Search the test suite for testRefreshModuleAlias and run this fine-grained case using the files shown in the issue. Trace how changing b.py to b.py.2 affects the alias imported by a.py. Done means the case passes with the expected output shown, including the reported module-attribute error.

Written by the indexing model from the issue text.

Description

bug priority-1-normal topic-fine-grained-incremental

We don't track changes to module aliases correctly. This test case fails currently:

[case testRefreshModuleAlias]
import a
a.n.x
[file a.py]
from b import m
n = m
[file b.py]
import m
[file b.py.2]
import m2 as m
[file m.py]
x = 1
[file m2.py]
[builtins fixtures/module.pyi]
[out]
==
main:2: error: Module has no attribute "x"
Dominant language
Python
Stars
20.6k
Forks
3.3k
Avg merge
1d 18h
Merged PRs (30d)
54

Contributor guide

Open the contributing guide

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 python/mypy

All issues in python/mypy

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.