Skip to content

BUG/ENH: Passing explicit dtype should delegate to appropriate Index subclass (if available) #5196

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
jtratner opened this issue Oct 12, 2013 · 2 comments
Assignees
Labels
Bug Indexing Related to indexing on series/frames, not to indexes themselves
Milestone

Comments

@jtratner
Copy link
Contributor

e.g. here's wrong behavior on current master

In [1]: import pandas as pd
In [2]: ind = pd.Index([1, 2, 3], dtype='int64')
In [3]: ind
Out[3]: Index([1, 2, 3], dtype='object')

Problem is ordering of how passed dtypes work in Index constructor. Make sure this gets fixed in 0.14.

@jtratner
Copy link
Contributor Author

I'm punting this to 0.14 - too much of internals rely on this behavior right now and it's clearly not that big of a deal. I think it may just resolve itself when index isn't ndarray (because I think it's either hitting weirdness with numpy methods OR there's a case where we expect to be passing values are are instead passing Index)

@jreback jreback closed this as completed Jan 3, 2014
@jreback jreback reopened this Jan 3, 2014
@jreback jreback modified the milestones: 0.15.0, 0.14.0 Mar 28, 2014
@jreback jreback modified the milestones: 0.16.0, Next Major Release Mar 3, 2015
@sinhrks sinhrks modified the milestones: 0.17.0, Next Major Release Sep 11, 2015
@sinhrks
Copy link
Member

sinhrks commented Sep 11, 2015

Closed by #11017.

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 a pull request may close this issue.

3 participants