-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
on 32bit -- Series is int64 but cut produces int32 series #14866
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
hmm, this should always be |
re new tests: yeap -- trying to build current master thus version is |
yeah for some reason our git describe is off, not really sure why |
normally things like this would show up on windows, but this is ok there. |
so what should we do about this one? on my end I know only asmuch as do astype in the test to workaround ;) |
@yarikoptic if you want to debug and see where the 32bit is coming from, great. we don't test on 32-bit systems any longer. |
closes pandas-dev#14866 xref pandas-dev#14183 Author: Jeff Reback <[email protected]> Closes pandas-dev#15766 from jreback/32bit and squashes the following commits: 93c03e3 [Jeff Reback] BUG: 32bit compat for .get_indexer 4163918 [Jeff Reback] BUG: fix isin for 32bit platform issues 1bb2f60 [Jeff Reback] BUG: cut/qcut should always return int64 bins
Code Sample, a copy-pastable example if possible
failing on 32bit test
Problem description
orig: https://buildd.debian.org/status/fetch.php?pkg=pandas&arch=i386&ver=0.19.1%2Bgit174-g81a2f79-1&stamp=1481436461 (still don't know about "bad argument to internal function" -- can't replicate locally, so ignore for this one):
so I guess if Series should use int64 regardless of underlying architecture default type, then cut should also produce int64, I guess.... or should Series have arch-default int??
The text was updated successfully, but these errors were encountered: