#25636 closed Cleanup/optimization (fixed)
drop support for SpatiaLite < 3.0
| Reported by: | Sergey Fedoseev | Owned by: | Sergey Fedoseev |
|---|---|---|---|
| Component: | GIS | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Ready for checkin | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
This will make code cleaner and will make possible to get SRIDs from the backend.
Change History (12)
comment:1 by , 9 years ago
| Owner: | set to |
|---|---|
| Status: | new → assigned |
comment:2 by , 9 years ago
| Summary: | drop support to SpatiaLite < 3.0 → drop support for SpatiaLite < 3.0 |
|---|---|
| Triage Stage: | Unreviewed → Accepted |
comment:3 by , 9 years ago
comment:4 by , 9 years ago
If compare with PostGIS, PostGIS 2.1 is only available in latest Debian stable and Ubuntu LTS, these releases ship SpatiaLite 4.1. Any objections to drop support even for SpatiaLite < 4.0/4.1?
comment:5 by , 9 years ago
I'm not very enthusiast about dropping both 2.4 and 3 versions in Django 1.10. Let's begin by dropping 2.x only.
comment:7 by , 9 years ago
| Patch needs improvement: | set |
|---|
comment:8 by , 9 years ago
| Patch needs improvement: | unset |
|---|---|
| Triage Stage: | Accepted → Ready for checkin |
Created #25645 as a reminder to evaluate dropping SpatiaLite < 4.0 in Django 1.11.
Note:
See TracTickets
for help on using tickets.
Fine for me (and ignore my comment on #25631).