Practical issue to track the progress of deprecations required for https://github.com/shapely/shapely-rfc/pull/1, and keep an overview of this: - [x] Mutability of geometries -> https://github.com/Toblerity/Shapely/pull/900 - [x] Proxy/adapter classes -> https://github.com/Toblerity/Shapely/pull/926 - [x] Iteration / getitem of multi-part geometries -> https://github.com/Toblerity/Shapely/pull/950 - [x] From that PR: deprecate `__len__` as well? -> #1075 - [x] The array_interface and ctypes attribute -> https://github.com/Toblerity/Shapely/pull/955 - [x] Empty geometries: - The constructors can probably "just" change behaviour in 2.0? - The `EmptyGeometry` class (this one would also be fine to only deprecate in 2.0 -> https://github.com/Toblerity/Shapely/issues/1022) - [x] STRTree (for this the exact change still needs to be decided in the RFC) -> https://github.com/Toblerity/Shapely/pull/1064 - [x] Setting custom attributes -> #1183
Practical issue to track the progress of deprecations required for shapely/shapely-rfc#1, and keep an overview of this:
__len__as well? -> Deprecate len(..) of multi-part geometries #1075EmptyGeometryclass (this one would also be fine to only deprecate in 2.0 -> Shapely 2.0: deprecate BaseGeometry() and EmptyGeometry() ? #1022)