-
-
Notifications
You must be signed in to change notification settings - Fork 18.1k
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: series created from pyarrow array with date32 type in 1.5rc0 can be created but not displayed #48238
Comments
Thanks for the report! I was able to replicate this issue as well. |
One point of note: the |
Gotcha - what’s the right way to make a pd object from arrow array then? Or is only the “non-arrow data -> pd object construction-> pandas manages arrow conversion” path supported? |
I'll make sure there's some documentation around using
|
Noting that this was fixed by https://github.com/pandas-dev/pandas/pull/48489/files and should be fixed when 1.5 is released. Just needs a unit test |
Is the test needed as simple as just making an appropriate series and calling repr()? Basically, is this issue something a first-time contributor could do? |
Yeah @a-reich essentially this test needs to be added which hopefully should be a good first time contribution: https://github.com/pandas-dev/pandas/pull/48258/files#diff-290226273f5cd28655f0fa2a4c154cd9909edc6a1f5abee07fec8ab374a9133eR1755 |
take |
looks like this works but just needs a test? removing from the 2.0 milestone then |
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
I saw in the "what's new" for the new release the functionality for creating general Arrow-backed objects and wanted to try it out. So I created a simple test Arrow
Array
withdate32
type and tried to make a series from it as described, but the series cannot be displayed without erroring. Theser
value itself can be created and its array values accessed still.This issue didn't occur with eg
pa.int32
but I did not comprehensively test across Arrow data types.And while I'm here, thank you to the team for all your work on the awesome Arrow integration/extension features!
Expected Behavior
ser
can be displayed in an interactive REPL as usual andrepr(ser)
does not error.Installed Versions
INSTALLED VERSIONS
commit : 224458e
python : 3.10.1.final.0
python-bits : 64
OS : Windows
OS-release : 10
Version : 10.0.19044
machine : AMD64
processor : Intel64 Family 6 Model 78 Stepping 3, GenuineIntel
byteorder : little
LC_ALL : None
LANG : None
LOCALE : English_United States.1252
pandas : 1.5.0rc0
numpy : 1.23.2
pytz : 2022.2.1
dateutil : 2.8.2
setuptools : 60.2.0
pip : 21.3.1
Cython : None
pytest : None
hypothesis : None
sphinx : None
blosc : None
feather : None
xlsxwriter : None
lxml.etree : None
html5lib : None
pymysql : None
psycopg2 : None
jinja2 : None
IPython : 7.31.0
pandas_datareader: None
bs4 : None
bottleneck : None
brotli :
fastparquet : None
fsspec : None
gcsfs : None
matplotlib : None
numba : None
numexpr : None
odfpy : None
openpyxl : None
pandas_gbq : None
pyarrow : 8.0.0
pyreadstat : None
pyxlsb : None
s3fs : None
scipy : None
snappy : None
sqlalchemy : None
tables : None
tabulate : None
xarray : None
xlrd : None
xlwt : None
zstandard : None
tzdata : None
The text was updated successfully, but these errors were encountered: