[vtk-developers] Update: Making Tests Python 3/2 compatible.

[David Gobbi]

On Mon, Aug 10, 2015 at 8:05 AM, Matthew Brett <matthew.brett at gmail.com>
wrote:

> Hi,
>
> On Mon, Aug 10, 2015 at 3:01 PM, David Gobbi <david.gobbi at gmail.com>
> wrote:
> > Very nice.  On my machine I see only six failures.  This is with Python
> 3.2,
> > and apparently no NetCDF.
> >
> > The following tests FAILED:
> > 354 - vtkCommonDataModelPython-TestTemplates (Failed)
> > 969 - vtkFiltersSourcesPython-squadViewer (Failed)
> > 1944 - vtkRenderingTkPython-cursor3D (Failed)
> > 1945 - vtkRenderingTkPython-TestTextActor3D (Failed)
> > 1946 - vtkRenderingTkPython-TestTkRenderWidget (Failed)
> > 1947 - vtkRenderingTkPython-TestTkRenderWindowInteractor (Failed)
> >
> > The TestTemplates seems to be a simple syntax error, the "u" string
> prefix
> > is not allowed in python 3.2.
> >     354:   File "Common/DataModel/Testing/Python/TestTemplates.py", line
> 56
> >     354:     value = u"hello"
>
> Is it worth requiring Python 3.3 or higher to fix this?   I doubt
> you'll have many Python 3.2 users, even if you released now - Python
> 3.4 has been around for a while now.
>

Out of hundreds of python tests there's a single line that won't work with
Python 3.2, and you people are clamouring to drop Python 3.2.  Honestly,
what's up with that?

I wouldn't be testing on Python 3.2 if I didn't think it would be worth
supporting.  There are still plenty of deployed systems around
(particularly Ubuntu and Debian) that come with Python 3.2 packages, and
they're far from End of Life.  And honestly, supporting Python 3.2 doesn't
take much effort.

 - David
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20150810/92d1a4b8/attachment.html>