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
Setting back pandas 2.1.4 doesn't fix the issue, so it is due to GDAL.
It appears as if GDAL now writes right indented numbers instead of left indented or something.
I think testing strings are identical here defeats the purpose, important is that GDAL can read the file and interprets the file equal as if it were written with GDAL. Replacing assert_equal_content with the following code fixes the errors:
Fixes#774
# Description
Build in #760 fails for
test_rasterio_ascii
``test_rasterio_ascii`` doesn't work for GDAL 3.8.3 compared to 3.7.3.
Previously it was tested if files are exactly identical. This defeats
the purpose, more important is that GDAL can read the file and
interprets the file equal as if it were written with GDAL. Replacing
``assert_equal_content`` with the changes fixes things.
# Checklist
<!---
Before requesting review, please go through this checklist:
-->
- [x] Links to correct issue
- [ ] Update changelog, if changes affect users
- [x] PR title starts with ``Issue #nr``, e.g. ``Issue #737``
- [x] Unit tests were added
- [ ] **If feature added**: Added/extended example
Build in #760 fails for
test_rasterio_ascii
Relevant updates in lock file are:
GDAL 3.7.3 -> 3.8.3
pandas 2.1.4 -> 2.2.0
Setting back pandas 2.1.4 doesn't fix the issue, so it is due to GDAL.
It appears as if GDAL now writes right indented numbers instead of left indented or something.
I think testing strings are identical here defeats the purpose, important is that GDAL can read the file and interprets the file equal as if it were written with GDAL. Replacing
assert_equal_content
with the following code fixes the errors:The text was updated successfully, but these errors were encountered: