You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a pipe dream for now, the code base is quite large, only a small part of it has been typed so far.
There are various bugs which are easily revealed by adding function types, and then having Ruff/Pyright take a look at the errors.
Since the original codebase is Python 2, the code was not written with types in mind.
It would be nice to have some test that ensured that everything is typed - maybe Ruff/Pyright have a rule we could use for this?
At least a soft-error/warning one that would inform about the amounts of issues in the various files.
This would also possibly include having types in the libraries we depend on, some of which are tiny.
That will most likely require us to send them a PR.
The text was updated successfully, but these errors were encountered:
This is a pipe dream for now, the code base is quite large, only a small part of it has been typed so far.
There are various bugs which are easily revealed by adding function types, and then having Ruff/Pyright take a look at the errors.
Since the original codebase is Python 2, the code was not written with types in mind.
It would be nice to have some test that ensured that everything is typed - maybe Ruff/Pyright have a rule we could use for this?
At least a soft-error/warning one that would inform about the amounts of issues in the various files.
This would also possibly include having types in the libraries we depend on, some of which are tiny.
That will most likely require us to send them a PR.
The text was updated successfully, but these errors were encountered: