[Gdal-dev] Re: GDAL's Python Identity Crisis (was Re: Import Gdal)
Brian Hamlin
maplabs at light42.com
Fri Sep 21 03:47:28 EDT 2007
On Sep 20, 2007, at 9:59 PM, Christopher Barker wrote:
>
>> I think we should only do this for the next-gen bindings,
>
> I agree, though it might be better from a confusion stand point to
> have them both the same -- I'm really not sure.
Why not leave the old name space with the old Python bindings, and
preserve the old test suite in a folder with those names, all as
legacy. Then the new namespace goes with the new bindings and (perhaps
the same) tests but in a new folder with the new invocation. Sounds
like a clean setup.
That way if you ever look at a test file, you know for certain which
generation you are looking at.
ps- extra bonus, do that for 1.5 and leave 1.4.3 working as it stands :)
caveat - I dont use Python much
best regards
-Brian
More information about the Gdal-dev
mailing list