Bug 1794282

python-geopandas fails to build with Python 3.9.0a2.

The pytest log is too long to past here, but hare s the header:

platform linux -- Python 3.9.0a2, pytest-4.6.9, py-1.8.0, pluggy-0.13.0
rootdir: /builddir/build/BUILD/geopandas-0.6.0, inifile: setup.cfg
collected 853 items / 1 deselected / 1 skipped / 851 selected
geopandas/io/tests/test_file.py .................                        [  1%]
geopandas/io/tests/test_file_geom_types_drivers.py ..................... [  4%]
.....................                                                    [  6%]
geopandas/io/tests/test_infer_schema.py ....................             [  9%]
geopandas/io/tests/test_sql.py sssss..                                   [ 10%]
geopandas/tests/test_api.py .                                            [ 10%]
geopandas/tests/test_array.py .....................................FFFFF [ 15%]
FFF......................................                                [ 19%]
geopandas/tests/test_config.py ..                                        [ 20%]
geopandas/tests/test_crs.py .....................                        [ 22%]
geopandas/tests/test_datasets.py ...                                     [ 23%]
geopandas/tests/test_dissolve.py ......                                  [ 23%]
geopandas/tests/test_extension_array.py ................................ [ 27%]
........................................................................ [ 35%]
..........x....sss.......s....................ss............xxxxxxxxxxxx [ 44%]
.........................s.....sssssssssssssssssss...................... [ 52%]
..........................................sssssss..........ss            [ 59%]
geopandas/tests/test_geodataframe.py .........................ss........ [ 64%]
.........x.                                                              [ 65%]
geopandas/tests/test_geom_methods.py ................................... [ 69%]
.........................                                                [ 72%]
geopandas/tests/test_geoseries.py ..........................             [ 75%]
geopandas/tests/test_merge.py ...                                        [ 75%]
geopandas/tests/test_overlay.py .......................................s [ 80%]
.....................                                                    [ 82%]
geopandas/tests/test_pandas_methods.py .................xxX...           [ 85%]
geopandas/tests/test_plotting.py .........................ssssssss...... [ 90%]
.                                                                        [ 90%]
geopandas/tests/test_show_versions.py ....                               [ 90%]
geopandas/tests/test_sindex.py ..........s                               [ 92%]
geopandas/tests/test_testing.py ....                                     [ 92%]
geopandas/tests/test_types.py ...............                            [ 94%]
geopandas/tools/tests/test_sjoin.py ..................................xs [ 98%]
..                                                                       [ 98%]
geopandas/tools/tests/test_tools.py .........s                           [100%]

None of the failures seems familiar to 3.9 incompatibilities. Mostly it is assert equal_geometries(result, expected) that fails.


For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/@python/python3.9/fedora-rawhide-x86_64/01173058-python-geopandas/

For all our attempts to build python-geopandas with Python 3.9, see:
https://copr.fedorainfracloud.org/coprs/g/python/python3.9/package/python-geopandas/

Testing and mass rebuild of packages is happening in copr. You can follow these instructions to test locally in mock if your package builds with Python 3.9:
https://copr.fedorainfracloud.org/coprs/g/python/python3.9/

Let us know here if you have any questions.

Python 3.9 will be included in Fedora 33. To make that update smoother, we're building Fedora packages with early pre-releases of Python 3.9.
A build failure prevents us from testing all dependent packages (transitive [Build]Requires), so if this package is required a lot, it's important for us to get it fixed soon.
We'd appreciate help from the people who know this package best, but if you don't want to work on this now, let us know so we can try to work around it on our side.