-
Notifications
You must be signed in to change notification settings - Fork 680
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
[Housekeeping] mypy flytekit cleanup #1030
Comments
There are too many errors, I broke out this task into more granular ones:
Feel free to add more details/edits to those as needed |
pls assign me I would like to work on this |
@wild-endeavor @pingsutw, has the issue been resolved? |
@samhita-alla is this issue still open - if so, I don;t mind fixing a few of these for hacktoberfest. Also, i can see some issues #1427 #1447 related to this closed, with associate PR merged in.a year ago but i can still see some mypy errors related to
|
Thank you @ryankarlos, we still have some linting errors which aren't fixed yet. Feel free to open a pr in the flytekit repo 😄 |
Thanks @pingsutw , ive run |
yeah, I prefer to split these between multiple PRs, which will be easy to review. |
thanks im working on a PR. do you labelling this issue with hacktoberfest label 😄 @samhita-alla |
@pingsutw, is it okay to close this PR or are there any more fixes that need to go in? |
Still have some mypy errors needed to be fixed. @ryankarlos is working on it. |
@pingsutw I may not get around to fixing the others immediately - as got a few other PRs to complete as well. Feel free to unassign me if someone else wants to tackle some of the remaining. |
Describe the Issue
Wholesale cleanup of mypy warnings and errors in flytekit. Larger items like tuple support should have standalone tickets created.
What if we do not do this?
Flytekit remains unpolished.
Related component
flytekit
The text was updated successfully, but these errors were encountered: