10000 Pin mypy version to 1.6.* by Alnusjaponica · Pull Request #5123 · optuna/optuna · GitHub
[go: up one dir, main page]

Skip to content

Pin mypy version to 1.6.* #5123

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

Merged
merged 5 commits into from
Nov 26, 2023
Merged

Conversation

Alnusjaponica
Copy link
Contributor
@Alnusjaponica Alnusjaponica commented Nov 18, 2023

Motivation

Temporary fix Checks(integration) by adding version specification on mypy

Description of the changes

It appears that mypy v1.7.0 is causing significant regressions when used in 8000 conjunction with pybind11, upon which mypy's type inference for torch modules depends. This issue is highlighted in python/mypy#16486.
This pull request addresses the problem by setting the mypy version to v1.6.* until the associated bugs are resolved, as Pytorch does here.

Alternatives

Add type:ignores and wait for the warn-unused-ignores option to detect that the bug has been resolved.

Copy link
codecov bot commented Nov 18, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (a37b4ce) 89.32% compared to head (bbd6192) 89.32%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #5123   +/-   ##
=======================================
  Coverage   89.32%   89.32%           
=======================================
  Files         205      205           
  Lines       15188    15188           
=======================================
  Hits        13566    13566           
  Misses       1622     1622           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@Alnusjaponica Alnusjaponica marked this pull request as ready for review November 19, 2023 8000 03:00
Copy link
Member
@not522 not522 left a comment

Choose a reason for hiding this comment

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

LGTM!

@not522 not522 removed their assignment Nov 21, 2023
@Alnusjaponica
Copy link
Contributor Author
8000 Alnusjaponica commented Nov 22, 2023

@HideakiImamura I resolved the conflict and revised the comment a little. Please take anther look.

Copy link
Member
@HideakiImamura HideakiImamura left a comment

Choose a reason for hiding this comment

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

LGTM.

@HideakiImamura HideakiImamura added this to the v3.5.0 milestone Nov 22, 2023
@HideakiImamura HideakiImamura added the other Issue/PR that does not fit into any other label. label Nov 22, 2023
@HideakiImamura HideakiImamura removed their assignment Nov 22, 2023
@HideakiImamura HideakiImamura merged commit f742a10 into optuna:master Nov 26, 2023
@Alnusjaponica Alnusjaponica deleted the pin-mypy-version branch November 30, 2023 01:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
other Issue/PR that does not fit into any other label.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
0