Skip to content

Use --no-implicit-optional for type checking#6413

Merged
datumbox merged 3 commits into
pytorch:mainfrom
hauntsaninja:implicit-optional
Aug 15, 2022
Merged

Use --no-implicit-optional for type checking#6413
datumbox merged 3 commits into
pytorch:mainfrom
hauntsaninja:implicit-optional

Conversation

@hauntsaninja

@hauntsaninja hauntsaninja commented Aug 13, 2022

Copy link
Copy Markdown
Contributor

This makes type checking PEP 484 compliant (as of 2018).
mypy will change its defaults soon.

See:
python/mypy#9091
python/mypy#13401

This is needed for PEP 484 compliant type checking (as of 2018).
mypy will change its defaults soon.

See python/mypy#9091
@datumbox
datumbox merged commit 4db84b0 into pytorch:main Aug 15, 2022
@github-actions

Copy link
Copy Markdown

Hey @datumbox!

You merged this PR, but no labels were added. The list of valid labels is available at https://github.com/pytorch/vision/blob/main/.github/process_commit.py

@datumbox datumbox added the other if you have no clue or if you will manually handle the PR in the release notes label Aug 15, 2022
@hauntsaninja
hauntsaninja deleted the implicit-optional branch August 15, 2022 17:51
facebook-github-bot pushed a commit that referenced this pull request Aug 24, 2022
Summary:
* Use --no-implicit-optional for type checking

This is needed for PEP 484 compliant type checking (as of 2018).
mypy will change its defaults soon.

See python/mypy#9091

* forcing CI rerun

Reviewed By: datumbox

Differential Revision: D38824221

fbshipit-source-id: 2f786faadaedd7eaf0dd2147a9c575d1d86c9db0

Co-authored-by: Vasilis Vryniotis <datumbox@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla signed code quality other if you have no clue or if you will manually handle the PR in the release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants