Skip to content

BUG: truncate has incorrect behavior when index has only one unique v… #42366

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 2 commits into from
Jul 8, 2021

Conversation

neelmraman
Copy link
Contributor

@neelmraman neelmraman commented Jul 4, 2021

…alue (#42365)

@jreback jreback added the Bug label Jul 4, 2021
@jreback jreback added this to the 1.4 milestone Jul 4, 2021
@jreback jreback added the Indexing Related to indexing on series/frames, not to indexes themselves label Jul 4, 2021
@jreback
Copy link
Contributor

jreback commented Jul 4, 2021

looks fine can you add a whatsnew note in 1.4 bug fixes, indexing section

@neelmraman
Copy link
Contributor Author

@jreback I think this PR should be good as well since the errors above seem transient and unrelated to any of the code changes here (and I'm seeing similar errors in other PRs)

@jreback jreback merged commit 8d64fe9 into pandas-dev:master Jul 8, 2021
@jreback
Copy link
Contributor

jreback commented Jul 8, 2021

thanks @neelmraman

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Indexing Related to indexing on series/frames, not to indexes themselves
Projects
None yet
Development

Successfully merging this pull request may close these issues.

BUG: truncate has wrong behavior when the Index has only one unique value
2 participants