You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@QuLogic thanks for the report!
Yes, I think it is indeed failing because of the reason you mention. In pygeos, there is a byte_order keyword to optionally force a certain byte-order (instead of using the native machine byte order), and this is used in the tests to have them robust for this. But in GeoPandas we currently don't expose that keyword.
Long term we could maybe expose such a keyword in the geopandas version as well. Short term it seems fine to just skip those tests on big-endian systems (since the important aspect about the test is that it is correctly calling shapely/pygeos, and the actual correctness of the WKB is tested by those underlying libraries)
Problem description
Possibly failing because it hard codes the byte representation of multi-byte integers?
Expected Output
Tests pass.
Versions
Python 3.10.0rc2
geopandas: 0.10.0
pandas: 1.3.0
Fiona: 1.8.20
NumPy: 1.21.1
Shapely: 1.7.1
rtree: 0.9.4
pyproj: 3.2.1
matplotlib: 3.5.0rc1
mapclassify: 2.4.3
geopy: N/A
psycopg2: 2.9.1
geoalchemy2: N/A
pyarrow: N/A
pygeos: N/A
The text was updated successfully, but these errors were encountered: