#19 migrate the code to python3

Ouvert
Créé il y a 7 ans par xcombelle · 1 commentaires

One have to think to migrate to python3 as end of life of python2 is 2020.

It should kill two bird with one stone at it should solve unicode problems show in #13 and #7

One have to think to migrate to python3 as end of life of python2 is 2020. It should kill two bird with one stone at it should solve unicode problems show in #13 and #7
pitchum a commenté il y a 7 ans
Collaborateur

I tried to migrate to python3 hoping it would be easy and I finally gave up. It would require a lot of rewriting, mostly because GeoAlchemy is not python3-compatble.

GeoAlchemy2 is python3-compatible but the API is quite different from GeoAlchemy. Moreover GeoAlchemy2 dropped support for sqlite+spatialite and only focuses on Postgresql+PostGIS.

I tried to migrate to python3 hoping it would be easy and I finally gave up. It would require a lot of rewriting, mostly because GeoAlchemy is not python3-compatble. GeoAlchemy2 is python3-compatible but the API is quite different from GeoAlchemy. Moreover GeoAlchemy2 dropped support for sqlite+spatialite and only focuses on Postgresql+PostGIS.
Connectez-vous pour rejoindre cette conversation.
Pas d'étiquette
bug
Aucun jalon
Pas d'assignataire
2 Participants
Chargement…
Annuler
Enregistrer
Il n'existe pas encore de contenu.