Even Rouault-2 wrote
> Mateusz already answered on that. Writing Python tests is faster/easier
> than C/C++ ones.
> We/I tend to limit C/C++ written tests to part of the API not available
> through the Python
> API.
Another point of view: Based on the number of questions that I have seen on
the
On Tue, 26 Sep 2017 15:27:59 +0100, Even Rouault
wrote:
On mardi 26 septembre 2017 15:08:09 CEST Joaquim Luis wrote:
>> P.S. - It seems strange to use python as a CI interface to a C/C++
>>
>> library. Is there a reason the test harness isn't in C/C++?
On mardi 26 septembre 2017 15:08:09 CEST Joaquim Luis wrote:
> >> P.S. - It seems strange to use python as a CI interface to a C/C++
> >>
> >> library. Is there a reason the test harness isn't in C/C++?
> >
> > Mateusz already answered on that. Writing Python tests is faster/easier
> > than
P.S. - It seems strange to use python as a CI interface to a C/C++
library. Is there a reason the test harness isn't in C/C++?
Mateusz already answered on that. Writing Python tests is faster/easier
than C/C++ ones. We/I tend to limit C/C++ written tests to part of the
API not
Hi Andrew,
> I'm trying to enable autotest so that I can easily verify changes I make to
> GDAL. I'm having difficulty as my familiarity with the python environment
> is limited. I don't think I want to install the swig bindings OVER the
> current GDAL interface code that I may have in my
On 26 September 2017 at 14:28, Andrew Bell wrote:
>
> P.S. - It seems strange to use python as a CI interface to a C/C++ library.
> Is there a reason the test harness isn't in C/C++?
Historical.
Python was obvious choice as simple platform.
Python kills two targets
I'm trying to enable autotest so that I can easily verify changes I make to
GDAL. I'm having difficulty as my familiarity with the python environment
is limited. I don't think I want to install the swig bindings OVER the
current GDAL interface code that I may have in my system python