-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adjust for mypy --no-implicit-optional
#465
Comments
4 tasks
khaeru
added a commit
that referenced
this issue
Nov 9, 2022
Satisfy mypy 0.990 in .base.Backend.get_log_level()
khaeru
added a commit
to iiasa/message_ix
that referenced
this issue
Nov 9, 2022
khaeru
added a commit
to iiasa/message_ix
that referenced
this issue
Nov 9, 2022
khaeru
added a commit
to iiasa/message_ix
that referenced
this issue
Nov 9, 2022
khaeru
added a commit
to iiasa/message-ix-models
that referenced
this issue
Feb 6, 2023
- Address no_implicit_optional within message_ix_models. - Work around iiasa/ixmp#465 via pyproject.toml.
4 tasks
khaeru
added a commit
that referenced
this issue
Nov 14, 2023
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As of mypy 0.990 (or 0.980, unclear),
--implicit-optional
is disabled by default. This results in type checking failures downstream, e.g. here inmessage_data
(private) with many messages like:As mitigation:
--implicit-optional
explicitly when type checking, e.g. in "lint" CI workflows for ixmp or downstream packages.As a fix:
The text was updated successfully, but these errors were encountered: