-
-
Notifications
You must be signed in to change notification settings - Fork 18.3k
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
BUG: loc[] returns object type instead of float #60600
Comments
Thanks for the report. I'd hazard a guess that we are determining the dtype of the result prior to column selection. Further investigations are welcome! |
take |
take |
Hi @parthi-siva and @DarthKitten2130 , |
Hi @sanggon6107 I'm still working on this.. |
Well noted. Thanks for the quick reply. |
for this input
as we can see that arr contains string so the datatype returned will be object only. Then we are creating empty numpy array using the dtype which will be of type object
Then we do slice using cpython function
After the func(arr, indexer, out, fill_value) call, the out array is populated with the selected elements. However, the dtype of out will not match the dtype of the elements in arr. I tried to add a step to check and adjust the dtype of out after the func call.
This fixed the op's issue but test cases are failing. Also I feel this is not a right way to address the issue So I'm not sure how to infer the dtype pragmatically before this for df.loc[0,[1,2]] |
Hi @parthi-siva, I had also tried similar thing, but it seems there could be side effects including test failures, since there could be many other pandas functions that call Proposed solution @final
def _getitem_lowerdim(self, tup: tuple):
...
# This is an elided recursive call to iloc/loc
out = getattr(section, self.name)[new_key]
# Re-interpret dtype of out.values for loc/iloc[int, list/slice]. # GH60600
if i == 0 and isinstance(key, int) and isinstance(new_key, (list, slice)):
inferred_dtype = np.array(out.values.tolist()).dtype
if inferred_dtype != out.dtype:
out = out.astype(inferred_dtype)
return out There was only one failing test when I locally ran Please let me know what you think about the proposal. I'd be glad to co-author a commit and make a PR if you don't mind. cc @rhshadrach Thanks! |
Hi @sanggon6107 , Thanks for the reply. Pls proceed with you proposal. I'm good! I spent some time regarding your concern about creating a can we try using either like this
or like this
Please let me know if it helps. |
@sanggon6107 - it's not clear to me what the proposal is. Best to open a PR I think. |
Hi @parthi-siva , your suggestion helped a lot! I've also found that we could simplify the code by using |
take |
Sure @sanggon6107 :) |
Pandas version checks
I have checked that this issue has not already been reported.
I have confirmed this bug exists on the latest version of pandas.
I have confirmed this bug exists on the main branch of pandas.
Reproducible Example
Issue Description
df.loc[0,[1,2]]
results in a Series of typedtype('O')
, whiledf[[1,2]].loc[0]
results in a Series of typedtype('float64')
.Expected Behavior
I would expect
df.loc[0,[1,2]]
to be of typefloat64
, same asdf[[1,2]].loc[0]
. The current behavior seems to encourage chaining instead of canonical referencing.Installed Versions
INSTALLED VERSIONS
commit : 0691c5c
python : 3.12.8
python-bits : 64
OS : Darwin
OS-release : 23.6.0
Version : Darwin Kernel Version 23.6.0: Thu Sep 12 23:35:10 PDT 2024; root:xnu-10063.141.1.701.1~1/RELEASE_ARM64_T6030
machine : arm64
processor : arm
byteorder : little
LC_ALL : None
LANG : en_US.UTF-8
LOCALE : en_US.UTF-8
pandas : 2.2.3
numpy : 1.26.4
pytz : 2024.1
dateutil : 2.9.0.post0
pip : 24.3.1
Cython : None
sphinx : 8.1.3
IPython : None
adbc-driver-postgresql: None
adbc-driver-sqlite : None
bs4 : 4.12.3
blosc : None
bottleneck : 1.4.2
dataframe-api-compat : None
fastparquet : None
fsspec : 2024.12.0
html5lib : 1.1
hypothesis : None
gcsfs : None
jinja2 : 3.1.5
lxml.etree : 5.3.0
matplotlib : 3.10.0
numba : 0.60.0
numexpr : 2.10.2
odfpy : None
openpyxl : 3.1.5
pandas_gbq : None
psycopg2 : None
pymysql : None
pyarrow : 18.1.0
pyreadstat : None
pytest : 8.3.4
python-calamine : None
pyxlsb : None
s3fs : 2024.12.0
scipy : 1.14.1
sqlalchemy : 2.0.36
tables : 3.10.1
tabulate : 0.9.0
xarray : 2024.11.0
xlrd : None
xlsxwriter : None
zstandard : 0.23.0
tzdata : 2024.2
qtpy : N/A
pyqt5 : None
The text was updated successfully, but these errors were encountered: