Hi David,
>> On top of all this, I wonder why you insist on a particular Python
>> version here: I tried your single testcase and it PASSes just as
>> well
>> with Python 2.7!? One reason I'm asking is that Solaris 11.3
>> bundles
>> both Python 2.7 and 3.4, but (unlike Linux and Solaris 11.4) don't
>> have /usr/bin/python3, just python (which is 2.7), python2.7, and
>> python3.4. Not that it matters too much, but you should be aware
>> of
>> the issue.
>
> In particular, given the differences between Python 2 and Python 3 I
> think it's a good idea to be explicit about the versions of Python that
> we expect i.e. are such tests coded to the common subset of Python 2
> and 3, or just to Python 3? Given that they're intended to be
> optional, I suggest just Python 3. (I would like to be able to add
> other Python-based scripts to the DejaGnu suite e.g. to verify JSON
> output, hence I'd prefer to not have to maintain Python 2
> compatibility)
understood. The whole Python 2 vs. 3 situation is a mess,
unfortunately, but I expect that all systems we deal with that have
Python at all will have some version of Python 3 around, and moving
forward Python 2 will phase out over time given the lack of upstream
support. Dealing with both at the current time seems a waste of time.
The only possible challenge may be to determine a python3 executable,
given that this exact name seems not to be ubiquitious. Maybe there's
an autoconf macro that does the necessary work instead of having to do
this in the testsuite directly?
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
