-
-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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
DOC: update PeriodArray docstring #37251
Conversation
@@ -67,7 +67,7 @@ class PeriodArray(PeriodMixin, dtl.DatelikeOps): | |||
""" | |||
Pandas ExtensionArray for storing Period data. | |||
|
|||
Users should use :func:`period_array` to create new instances. | |||
Users should use :func:`period_range` to create new instances. |
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.
period_array is correct
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.
It's not public, see also the linked issue
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.
@arw2019 thanks for the PR.
I would also mention pd.array(..)
as the way to create a PeriodArray from a sequence of Period scalars.
Added |
Thanks for the update! |
Small development related comment: can you generally try to avoid rebasing / force pushing to a branch, but rather only add new commits? (which means merging master instead of rebasing to update to latest master) Github works better that way (eg you can specifically see the new changes since your last review) making reviewing easier. |
black pandas
git diff upstream/master -u -- "*.py" | flake8 --diff