Skip to content

Make mypy --no-implicit-optional clean for strict Optional-checked files#3699

Merged
gvanrossum merged 4 commits intomasterfrom
mypy-no-implicit-optional
Jul 12, 2017
Merged

Make mypy --no-implicit-optional clean for strict Optional-checked files#3699
gvanrossum merged 4 commits intomasterfrom
mypy-no-implicit-optional

Conversation

@ddfisher
Copy link
Copy Markdown
Collaborator

No description provided.

@gvanrossum gvanrossum changed the title Make mypy --no-implicit-optinal clean for strict Optional-checked files Make mypy --no-implicit-optoinal clean for strict Optional-checked files Jul 12, 2017
@gvanrossum
Copy link
Copy Markdown
Member

I tried to look into the 3.5.1-specific failure. It's related to the premature evaluation of forward declarations in typing.py. IIRC their processing changed quite a bit between 3.5.1 and 3.5.2.

I noticed you replaced several occurrences of 'mypy.types.Type' with Optional['mypy.types.Type']. I wonder if replacing those with 'Optional[mypy.types.Type]' would fix the issue.

To test this locally you'll have to install Python 3.5.1 from python.org.

@JelleZijlstra JelleZijlstra changed the title Make mypy --no-implicit-optoinal clean for strict Optional-checked files Make mypy --no-implicit-optional clean for strict Optional-checked files Jul 12, 2017
Copy link
Copy Markdown
Member

@gvanrossum gvanrossum left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LG, needs merge and then hopefully the Appveyor tests will run.

@gvanrossum gvanrossum merged commit 65aedb5 into master Jul 12, 2017
@gvanrossum gvanrossum deleted the mypy-no-implicit-optional branch July 12, 2017 23:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants