`x = x or y` with x undeclared gives no error

Open
#937 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reproducing the reported x = x or y case in mypy and compare it with Python's handling of recursive definitions. The issue does not name a source file, test, expected diagnostic, or specific entry point, so completion criteria will need to be established before implementation.

Written by the indexing model from the issue text.

Description

bug priority-1-normal topic-runtime-semantics topic-variable-scope

I think it should, because python considers such recursive definitions to be an error.

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.