-
Notifications
You must be signed in to change notification settings - Fork 646
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
The Witness: mypy compliance #3112
Conversation
Update: Probably won't actually add my world to the list of files because the remaining errors are with core and the strategy seems to be "If there's something wrong with core that is stopping you from being mypy compliant, hopefully that'll motivate you to go and add typing to core", which it does not, for me. :D I'll still try to get this merged because I think it makes the Witness apworld better. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes LGTM. Compared generations before and after, had two questions about new code that were addressed. The new errors are reachable and work properly.
* Make witness apworld mostly pass mypy * Fix all remaining mypy errors except the core ones * I'm a goofy stupid poopoo head * Two more fixes * ruff after merge * Mypy for new stuff * Oops * Stricter ruff rules (that I already comply with :3) * Deprecated ruff thing * wait no i lied * lol super nevermind * I can actually be slightly more specific * lint
There are two remaining errors I cannot solve without touching core (I believe).
This PR will be drafted for now until the mypy PR is merged / rejected / finalised.