Skip to content

unique docstring extend #13565 unique datetime tz issue #14045

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

Closed
wants to merge 1 commit into from

Conversation

paulgueltekin
Copy link

closes #13565
whatsnew
extended doc string for unique addressing the issue with timezone aware datetimes ( see #13565 )

@jreback jreback closed this Aug 19, 2016
@jreback
Copy link
Contributor

jreback commented Aug 19, 2016

not this not correct. documenting this is silly when it can easily be fixed.

@paulgueltekin
Copy link
Author

I thought it can't be fixed easily / its the expected behavior (your own words) so i added a the docstring.

@jreback
Copy link
Contributor

jreback commented Aug 19, 2016

well its the 'expected behavior' because of numpy silliness

@jorisvandenbossche
Copy link
Member

@paulgueltekin Thanks for the PR! I think it would be good to document this if we leave it as is (even when it is due to limitations of numpy). However, we are now thinking that we will return an object array of Timestamps (which can still hold the timezone information), and in that case this PR is not needed (see PR #13979 (comment))

@jorisvandenbossche jorisvandenbossche added this to the No action milestone Aug 21, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Call unique() on a timezone aware datetime series returns non timezone aware result
3 participants