Skip to content

BUG: Refine validation of parameters to RangeIndex.__init__ #12295

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

toobaz
Copy link
Member

@toobaz toobaz commented Feb 11, 2016

closes #12288

stop : int (default: 0)
step : int (default: 1)
name : object, optional
Name to be stored in the index
copy : bool, default False
Make a copy of input if its a RangeIndex
Unused, accepted for homogeneity with other index types.
Copy link
Contributor

Choose a reason for hiding this comment

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

no, this is not right

@jreback
Copy link
Contributor

jreback commented Feb 12, 2016

I updated the issue.

@jreback jreback added Bug Indexing Related to indexing on series/frames, not to indexes themselves labels Feb 12, 2016
@jreback jreback added this to the 0.18.0 milestone Feb 12, 2016
@jreback jreback closed this in 1ca094f Feb 12, 2016
@jreback
Copy link
Contributor

jreback commented Feb 12, 2016

thanks. added some more tests, pls duplicate (or could refactor) for testing on other numeric indexes w.r.t. name propogation. Best would be to move this to Base as then will test for all indexes.

@toobaz toobaz deleted the rangeindexparams branch February 12, 2016 15:39
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.

RangeIndex copy behaviour differs from other indices
2 participants