Python 3.6 and 3.7 EOL

Development
1

So Python 3.6 is EOL this month. We still notionally support 3.4 (though even 3.5 isn’t actively tested), so is it OK to change this:

set(vtk_python_min_version "3.4")
set(vtk_python_version_support "3.6")

to:

set(vtk_python_min_version "3.4")
set(vtk_python_version_support "3.7")

where min_version is what is required, but below version_support, VTK’s configure makes noise unless VTK_LEGACY_SILENT. I’ll note that VTK_LEGACY_REMOVE raises min_version to version_support if set.

Thoughts?

2

Is there any opposition to doing this for 9.3 and adding 3.7 as well (now also EOL)? 3.6 and 3.7 will still be supported but only from source builds (like 3.4 and 3.5 are today), but wheels will not be published or tested as part of CI.

2 Likes
3

For reference, i the next few days we plan to integrate MR-10405 removing support for testing and publishing VTK python wheels for both Python 3.6 and 3.7.

This page documents the status of each Python versions. See https://devguide.python.org/versions/

4

FYI @charly_bollinger @mwestphal

5

I’m all for it, as you know :slight_smile: