-
-
Notifications
You must be signed in to change notification settings - Fork 182
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
Make mypy copier --strict
pass
#1441
Comments
I want to see autorefine in the action of semi-auto-resolving this, as soon as it's ready. I want to get your code-reviewer feedback afterwards. |
Hey @bswck ! Thanks for this nice project Is it possible to propose a batch of small pull requests in order to fix specific mypy errors or would you prefer a single PR to fix all of them? |
Thanks for reaching out. If you want to fix this issue, then I guess you might make a single pull request with bulk fixes in logically separated commits, in line with the contributing guide. If you're asking about autorefine, it will aim to organize fixes of linting and typechecking errors into groups that can be separated into small pull requests for the ease of reviewing and preserving easily bisectable, clean, logically grouped SCM history. autorefine is a very big idea, but I am currently jobless and have no time nor money to take the effort all by myself. If you would like to help, let's get in touch. |
Resolved via #1527. |
Actual Situation
mypy copier --strict
fails with 68 errors in 7 files (checked 11 source files).Checked on compiled mypy 1.5.1, Python 3.8.17.
Desired Situation
mypy copier --strict
passes successfully.Proposed solution
Resolve all errors reported by mypy.
A followup to #1431.
The text was updated successfully, but these errors were encountered: