-
Notifications
You must be signed in to change notification settings - Fork 34
TYP: Type annotations overhaul, episode 2 #288
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
TYP: Type annotations overhaul, episode 2 #288
Conversation
I'm not really sure what's causing these test failures here 🤔 |
They're in main too |
37b9c7b
to
a522dbc
Compare
Co-authored-by: crusaderky <crusaderky@gmail.com>
I'll try to take a cursory look at this before the meeting today |
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.
thanks Joren, this looks great! I looked through the whole diff. Approval pending discussion of builtin subclasses in the community meeting. Some comments but nothing major
Co-authored-by: Lucas Colley <lucas.colley8@gmail.com>
Co-authored-by: lucascolley <lucas.colley8@gmail.com>
all good from the community meeting 👍 |
This is a WIP in progress, but feel free to say whatever you feel like saying about the stuff I've already touched at this point.
_internal
common/*
numpy
__init__
_aliases
_info
_typing
fft
linalg
torch.*
dask.array.*
(except for.fft
)Because
cupy
has nopy.typed
, and is too dynamic for pyright to analyse, it's pretty much impossible to annotatecupy.*
at the moment.I decided to skip
torch
for now; this PR is big enough already.relevant info about
bool | int | float | complex
:#291 (comment)