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
Currently stubtest is very happy to treat "py" files as sources of type definitions. This is very useful, because it makes it easy to check packages that have mixed inline types and stubs (that may depend on each other).
But it does mean there is some counterintuitive behaviour where you'd expect to see something like "failed to find stubs". Basically, is it possible to salvage #12889 , #12896 (without becoming complicated enough that behaviour is unpredictable)?
Should also look into resolving some of the differences in the mypy build. Not going into detail (this is mostly a reminder for myself), but here are some links: pandas-dev/pandas#47760 (comment) #13161 (comment)
The text was updated successfully, but these errors were encountered:
Currently stubtest is very happy to treat "py" files as sources of type definitions. This is very useful, because it makes it easy to check packages that have mixed inline types and stubs (that may depend on each other).
But it does mean there is some counterintuitive behaviour where you'd expect to see something like "failed to find stubs". Basically, is it possible to salvage #12889 , #12896 (without becoming complicated enough that behaviour is unpredictable)?
Should also look into resolving some of the differences in the mypy build. Not going into detail (this is mostly a reminder for myself), but here are some links:
pandas-dev/pandas#47760 (comment)
#13161 (comment)
The text was updated successfully, but these errors were encountered: