Repository navigation
Errors in MEOS cannot be caught #17
Description
Right now, any error produced in the underlying MEOS library cannot be caught and results in the program termination.
This not only includes runtime errors (for which the program should stop), but for any error reported by MEOS to abort the transaction and return to known state, such as trying to compare temporal geographic points with different SRID.
This issue is caused by the MEOS library exiting, and the unability to stop this from the python code. To solve it, it is likely that some changes are required in the MEOS codebase when used by PyMEOS, but more research in this is needed.
Activity
[-]Crashes in MEOS cannot be caught[/-][+]Errors in MEOS cannot be caught[/+]Diviloper commentedon Sep 4, 2023
Solved in #21.
The
pymeos_cffipackage exposes a series of exceptions that allows the user to capture the different errors that may occur in MEOS.Bump apt postgresql-server-dev to 16 in the test workflow