jorisvandenbossche commented on PR #35637: URL: https://github.com/apache/arrow/pull/35637#issuecomment-1560566310
> so not supporting that for the conda-forge builds would suck IMO Yes, but to be clear, we currently don't support it for any form of distribution (also not wheels), the user is required to download it manually. So while I also certainly would like to see this solved, it's not something where conda-forge is worse. Although it might be easier to solve for conda-forge: > I don't mind shipping arrow's vendored `WindowsZones.xml` in a pyarrow-specific location (i.e. site-packages/pyarrow; we can patch pyarrow to point to the right location). That should be possible yes (I think it doesn't even need to be in a pyarrow-specific location, it could also be in a "proper" location for data). Currently this would require a patch in the C++ code, with https://github.com/apache/arrow/issues/35600 it should be an easier patch in the pyarrow's `__init__.py` One issue with vendoring is that this doesn't make it easy to update the version / ensure you always have a recent tz database, also when installing an somewhat older pyarrow version. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
