Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Deprecate the shapely.geos module

See original GitHub issue

To do item for Shapely 1.8: find a way to raise deprecation warnings for functionality in the shapely.geos module (as this will be completely removed in Shapely 2.0). Although it’s not really documented / recommended, it will be used in practice I think.

Eg the WKTReader / WKTWriter (eg https://stackoverflow.com/a/29548439/653364), the lgeos object to directly access GEOS functions (eg https://gis.stackexchange.com/a/226912/9828, we also did this in geopandas https://github.com/geopandas/geopandas/blob/8be1fd8b2a0b7691031d59b3a54275304db8aaa9/geopandas/io/sql.py#L58)

Issue Analytics

State:
Created 3 years ago
Comments:5 (5 by maintainers)

Top GitHub Comments

1reaction

sgilliescommented, Jun 8, 2020

There’s nothing to be done for users who are tapping into the lgeos object, it’s going to be removed.

There are users of the format readers/writers, so let’s try to move them to shapely.wkt?

0reactions

mwtoewscommented, Jun 10, 2020

Are you thinking specifically for the WKT/WKB readers/writers?

We could also make sure that all options for which users now might have used those classes are fully exposed and documented in shapely.wkt/wkb for Shapely 1.8, so users can actually already migrate away from using shapely.geos directly for this use case before it gets removed.

Yes. For what it’s worth, decisions where these modules should be put were made back in #63, so they were put in shapyley.geos, rather than shapely.wkt and shapely.wkb.