Opened 17 years ago
Closed 16 years ago
#1917 closed defect (fixed)
Enable next-gen Python bindings by default in 1.5
Reported by: | hobu | Owned by: | hobu |
---|---|---|---|
Priority: | normal | Milestone: | 1.5.0 |
Component: | ConfigBuild | Version: | unspecified |
Severity: | normal | Keywords: | python |
Cc: | warmerdam |
Description
This bug is to track the enabling of the next-gen bindings for 1.5
Change History (5)
comment:1 by , 17 years ago
comment:2 by , 16 years ago
Cc: | added |
---|---|
Component: | default → ConfigBuild |
Keywords: | python added |
Owner: | changed from | to
Assign to Howard.
Howard, could you update with outstanding known issues?
comment:3 by , 16 years ago
- _gdalmodule.so from an old install can still be in the way
- Need to test using a copy of the GDAL_DATA as part of the bindings install
- Need to figure out numpy setuptools stuff if we can
comment:4 by , 16 years ago
I think this work is done. I haven't heard hardly anything throughout the betas about it.
There may still be a few issues with unclean installs over old-gen bindings.
I didn't do anything about including GDAL_DATA directly as part of the Python bindings.
Numpy is not *required*, but still highly recommended.
Close when ready as part of the 1.5 release and we'll open new bugs for anything after.
comment:5 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Bulk of the changes in r12448