Skip to content
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

CLN: de-privatize names in core.computation #29665

Merged
merged 6 commits into from
Nov 17, 2019

Conversation

jbrockmendel
Copy link
Member

Some annotations. I'm finding that annotations in this directory are really fragile; adding a type to one thing will cause a mypy complaint in somewhere surprising.

@gfyoung gfyoung added Clean Internals Related to non-user accessible pandas implementation labels Nov 17, 2019
Copy link
Member

@gfyoung gfyoung left a comment

Choose a reason for hiding this comment

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

While I'm not sure what the rationale was for de-privatizing (I've seen this now in a couple of PR's), the changes look good to me.

@jbrockmendel
Copy link
Member Author

While I'm not sure what the rationale was for de-privatizing

Adhering to the convention of respecting private names makes it easier to reason about the code

@jreback jreback added this to the 1.0 milestone Nov 17, 2019
@jreback jreback merged commit d3bfcdc into pandas-dev:master Nov 17, 2019
@jreback
Copy link
Contributor

jreback commented Nov 17, 2019

thanks

@jbrockmendel jbrockmendel deleted the cln-comp2 branch November 17, 2019 15:38
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
Clean Internals Related to non-user accessible pandas implementation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants