from .x import y causes "Name already defined" for x

Open
#3,735 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Reproduce the diagnostic using the a.py, b.py, and c.py example in the report, then trace how mypy handles the star imports and relative imports. Done means this example no longer reports a duplicate definition for x, while the reported import behavior remains correctly checked.

Written by the indexing model from the issue text.

Description

bug false-positive priority-1-normal

I believe this is different than https://github.com/python/mypy/issues/2135.

In this case, if I have a star import like...

#a.py
import * from b
import * from c

#b.py
from .x import y

#c.py
from .x import z

I get a "Name 'x' is already defined" error.

But the name x is not exported by b or c.

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.