ENH: is it worth fixing a warning from a third party library here about pandas

[mroeschke]

Thanks for the issue. How is the third party library calling pandas? Usually this indicates that the third party library needs to adjust their usage of pandas to avoid the warning

[quant12345]

@mroeschke geopandas. I wanted to fix this, but as I said, it turned out to be pandas rows(that is, when I click on the warning link, I get to the pandas file).

[mroeschke]

If you could share an entire traceback of where this warning happens that would be helpful

[quant12345]

@mroeschke updated the message.

for example, I run a test:

pytest geopandas/tests/test_extension_array.py::TestGetitem::test_getitem_series_integer_with_missing_raises[integer-array]

I get a warning:

geopandas/tests/test_extension_array.py::TestGetitem::test_getitem_series_integer_with_missing_raises[integer-array]
  /geopandas/.venv/lib/python3.10/site-packages/pandas/tests/extension/base/getitem.py:276: FutureWarning: Series.__getitem__ treating keys as positions is deprecated. In a future version, integer keys will always be treated as labels (consistent with DataFrame behavior). To access a value by position, use `ser.iloc[pos]`
    ser[idx]

[mroeschke]

I see thanks.

As you can see on the pandas main branch this has been addressed so I think this should go away from the geopandas test suite once pandas 3.0 comes out

pandas/pandas/tests/extension/base/setitem.py

Line 244 in 1165859

arr[idx] = arr[0]