-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
Integer dtype is promoted to int64 #2759
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
Comments
thanks - I checked for related issues but I didn't see that one - I'll close this one |
can u provide a small example of how u plan to use the different dtype frames? |
I have a dataset comprising two blocks: block A contains numerical variables (float64), block B contains indicator variables (aka dummy features aka one-hot encoding - preferably with dtype int8). I wanted to concatenate both blocks using Here is an example::
If I insert the columns of B into A it preserves the dtype::
|
reopening so this can be converted to a test case for 0.11 |
With the PR #2708, this works (I'll add as a test case)
|
I suspect you also want to do something like this:
|
cool - looking forward to #2708 being merged - thanks guys |
this is merged into master...ok to close? |
yep. closed, thanks! |
thanks guys - Pandas rocks! 2013/2/11 Wes McKinney [email protected]
Peter Prettenhofer |
It seems that DataFrame (both constructor and
astype
) promotes the dtypes np.int[8,16,32] to np.int64 ::I'm not sure whether this is a but or on purpose (if so, a note in the docstring would be great).
Is there a specific reason why this is the case (e.g. to accomodate NA values?). If there are no NA's in the frame, can the promotion be turned off?
The text was updated successfully, but these errors were encountered: