Closed gabrieldemarmiesse closed 1 year ago
I like the from __future__ import annotations
but unlike other __future__
it's not 100% sure that it will be the default in the future. See https://docs.python.org/3/library/__future__.html#id2 . If it gets rejected, then we will have to change the whole codebase so I'd prefer to avoid using it.
I like the
from __future__ import annotations
but unlike other__future__
it's not 100% sure that it will be the default in the future. See https://docs.python.org/3/library/__future__.html#id2 . If it gets rejected, then we will have to change the whole codebase so I'd prefer to avoid using it.
Makes sense. I'm not strongly opinionated on this.
Done @liormizr could I have another code review? I encourage your to use squash and merge as the merging option because otherwise master will be very messy, there are lots of commits in my pull request.
hi @liormizr I had some time this weekend and typed the whole public api. I also fixed some return types with Self that will now return the correct type if there is some subclassing (otherwise the type is not narrowed down, see https://peps.python.org/pep-0673/ ).
I also don't really understand why the unit tests are failing because I just changed the types of the functions, it should have no impact on unit testing.
@gabrieldemarmiesse I added to master a fix for the issue that broke the tests Can you please merge from master so we will rerun the tests?
Thanks
@liormizr done!
@liormizr can you re-review?
@liormizr is there something I can do to push this forward? I think I've adressed all the issues you mentionned.
Hi @gabrieldemarmiesse Sorry for keeping you waiting I had two crazy weeks Our local PyCon conference in one week, and after a personal vacation. I'll do a last quick view on the PR and update you on Sunday
Related to #128