0.14.0 broken initialization of WKTElements about geoalchemy2

[adrien-berchet]

Hi @lucaslcode
Thanks for the report and sorry for the inconvenience.
Could you tell me what is the type of your Polygon object please? And if you can provide a Minimal Working Example to reproduce this error it would be nice.

[adrien-berchet]

Isn't it a Shapely object? If it is you should create your WKTElement by passing the wkt form of the geometry object, not the raw object. For example:

obj = shapely.wkt.loads("POLYGON((0 0, 0 1, 1 1, 1 0, 0 0))")
elem = WKTElement(obj.wkt)

[lucaslcode]

Thank you, it is indeed a shapely polygon. Odd that this line was working before!

[adrien-berchet]

Yeah previously it could accept anything that can be cast to a str object while now it must be a str object. Nevertheless, we could explicitly try to cast it to str in the WKTElement constructor to keep the same behavior as before, which I never considered but can be convenient.

[shuttle1987]

I ran into this as well due to some buggy code that finally broke with this release, an issue that I think would have been easily spotted in the CI pipeline if this package had type annotations. Is there any interest in adding type annotations into this project?

[adrien-berchet]

Sure, that would be nice!
Does anyone have some time to add it? It will be hard for me to find time for this before several weeks. For now I'm just going to open an issue.