Replies: 1 comment
-
|
Hi @JonDHo. The reason is just that I have not yet found the time to adjust the pyroSAR code to GeoAlchemy2 > 0.14. The same holds for sqlalchemy < 2.0. Would you like to give it a go? Or do you know someone who would? At the moment I am unfortunately quite busy with other things and cannot predict when I would find the time myself. I would provide support of course. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Just a question rather than raising an issue. Is there any reason that GeoAlchemy2 is pinned to <0.14? I have some other packages which now require GeoAlchemy>=0.17 and pyroSAR is a bit of a blocker as a result. Thanks for your work, it is super useful!
Beta Was this translation helpful? Give feedback.
All reactions