Home Explore Help
Sign In
FFDN
/
ffdn-db
6
1
Fork 6
Files Issues 16 Pull Requests 0 Wiki
Labels Milestones
New Issue

#19 migrate the code to python3

Open
opened 7 years ago by xcombelle · 1 comments
xcombelle commented 7 years ago

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 commented 7 years ago
Collaborator

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.
Sign in to join this conversation.
Labels
Clear labels
bug enhancement
No Label
bug
enhancement
Milestone
Clear milestone
No Milestone
Assignee
Clear assignee
No assignee
2 Participants
Write Preview
Loading...
Cancel
Save
There is no content yet.