Skip to content

CLN: type annotations #29333

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

Merged
merged 6 commits into from
Nov 3, 2019
Merged

CLN: type annotations #29333

merged 6 commits into from
Nov 3, 2019

Conversation

jbrockmendel
Copy link
Member

Separating these out from the non-CLN work going on in/around these functions.

Copy link
Member

@WillAyd WillAyd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just as a general comment I think it would be better to fully annotate some methods rather than partially annotating a lot of methods. The real value in doing this is getting the hard ones reviewed; can always have newer contributors sprint on easier annotations

@@ -790,7 +790,7 @@ def _get_axes(group):
return group.axes


def _is_indexed_like(obj, axes):
def _is_indexed_like(obj, axes) -> bool:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think reasonable to annotate obj as FrameOrSeries here, unless the TypeVar doesn't work in which case a Union

@WillAyd WillAyd added the Typing type annotations, mypy/pyright type checking label Nov 2, 2019
@jbrockmendel
Copy link
Member Author

Just as a general comment I think it would be better to fully annotate some methods rather than partially annotating a lot of methods.

That's reasonable. How strong is this preference? i.e. when weighed against "its nice to do these separately from the other PR that makes non-typing changes in the same functions to have a simpler diff"

@jreback jreback added this to the 1.0 milestone Nov 2, 2019
@jreback
Copy link
Contributor

jreback commented Nov 2, 2019

Just as a general comment I think it would be better to fully annotate some methods rather than partially annotating a lot of methods.

That's reasonable. How strong is this preference? i.e. when weighed against "its nice to do these separately from the other PR that makes non-typing changes in the same functions to have a simpler diff"

I would rather merge quickly on correct changes that are non-controversial, rather block things. so actually happy to type the 'easy' things (of course nice for newcomers to do this too).

@WillAyd
Copy link
Member

WillAyd commented Nov 2, 2019 via email

Copy link
Member

@WillAyd WillAyd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jbrockmendel
Copy link
Member Author

green

@jbrockmendel
Copy link
Member Author

gentle ping. a couple of upcoming branches are going to have merge conflicts with this otherwise

@jreback jreback merged commit ecd315b into pandas-dev:master Nov 3, 2019
@jreback
Copy link
Contributor

jreback commented Nov 3, 2019

thanks

@jbrockmendel jbrockmendel deleted the cln5 branch November 3, 2019 17:29
Reksbril pushed a commit to Reksbril/pandas that referenced this pull request Nov 18, 2019
proost pushed a commit to proost/pandas that referenced this pull request Dec 19, 2019
proost pushed a commit to proost/pandas that referenced this pull request Dec 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Typing type annotations, mypy/pyright type checking
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants