Skip to content
This repository was archived by the owner on Apr 14, 2022. It is now read-only.

Fix None being reported as not defined in type hints #336

Merged
merged 1 commit into from
Nov 2, 2018

Conversation

jakebailey
Copy link
Member

Fixes #335.

I'm not sure if it's good or bad that a ConstantExpression is making it into LookupAnalysisSetByName, but checking for it before warning will prevent user-visible weirdness.

@jakebailey jakebailey merged commit 4aaa139 into microsoft:master Nov 2, 2018
jakebailey added a commit that referenced this pull request Dec 3, 2018
Fixes #442.
Replaces #429, which only masks the underlying True/False bug in #391.

I also removed the hack in #336 which checked for `ConstantExpression`.
@jakebailey jakebailey deleted the non-use-before-def branch February 14, 2019 20:12
jakebailey added a commit to jakebailey/python-language-server that referenced this pull request Nov 1, 2019
jakebailey added a commit to jakebailey/python-language-server that referenced this pull request Nov 1, 2019
Fixes microsoft#442.
Replaces microsoft#429, which only masks the underlying True/False bug in microsoft#391.

I also removed the hack in microsoft#336 which checked for `ConstantExpression`.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants