|
Notes |
|
|
(0034609)
|
|
Edson Tadeu M. Manoel
|
|
2015-06-25 14:10
|
|
+1
VTK is the last major dependency holding people back from moving to Python 3 (therefore, holding people back from using modern things in Python and from using MSVC 2015). |
|
|
|
(0034675)
|
|
Ben Boeckel (Kitware)
|
|
2015-07-07 15:31
|
|
There are plans for it, but no hard timeline for it.
As for more modern MSVC, using a system Python 2.7 with MSVC 2013 works fine (it's what some of our dashboards do). I imagine 2015 would be similar. |
|
|
|
(0034691)
|
|
James Booth
|
2015-07-08 06:20
(edited on: 2015-07-08 06:22) |
|
+1
Would it possible for you to share a few more details on the current plans you have for tackling the issue Ben? It may be something we in the Python community could assist with, if only we had some guidance on what the key issues are.
The lack of Python 3 support is starting to make us think of moving away from using VTK in our project (https://github.com/menpo/ [^]).
I would argue that Python 3 support is a move you must undertake at some point to remain relevant in the scientific Python community. It's true that many are still using Python 2, but so many packages now support Python 3 and so many little advantages are now piling up (@ operator, advanced tuple unpacking, fixes to long standing issue like integer division, built with modern Windows compilers*) that there will come a point where peopl in the scientific community will come to think as Python 3 as the norm - surely VTK doesn't want to be caught flat-footed when that happens?
* It doesn't matter if VTK happens to work well with newer compilers, other Py2 projects don't, and there is no guarantee that they should. The community as a whole being able to drop support for Python 2 and with it VS2008 will be a big improvement for all of us. That can only happen after a wholesale move to Python 3, which packages like VTK are currently holding back.
|
|
|
|
(0034692)
|
|
hadimm
|
|
2015-07-08 06:46
|
|
I would like to insist on the fact that the Python community can definitvely help you for the Python 3 port. We only need some guidance as James pointed it out.
In the meantime James, if you don't know yet, have a look at Vispy (https://github.com/vispy/vispy [^]) which one of the main goal is to bring easy 3D viz to the browser. |
|
|
|
(0034694)
|
|
Ben Boeckel (Kitware)
|
|
2015-07-08 09:52
|
|
David Gobbi is the main developer of the wrapping code. The current approach to Python wrapping in VTK uses old-style classes. The new approach, I believe, will be creating a PyTypeObject for each VTK class. I'm not sure of the status of that currently.
However, the Python code itself (and CPython code directly in the repo) does need updating. It should support Python2 and Python3 at the same time (I wouldn't be surprised if six is necessary). I also forsee problems with Python3's str since VTK does not guarantee utf-8 anywhere (at least that I've ever seen), so bytes objects might be the way to go for some APIs.
If you'd like to help, merge requests on GitLab (https://gitlab.kitware.com/vtk/vtk [^]) to add dual Python2/3 support to the Python code would be appreciated. Feel free to mention me on the MR and I'll do a review of it. |
|
|
|
(0034700)
|
|
David Gobbi
|
|
2015-07-08 13:07
|
|
|
Here's a brief status report. I have the wrappers compiling with new-style classes, but the new implementation still has several holes that need to be filled in. It'll be at least a week before I'm ready to post any code. This will be the first (and probably the most crucial) step towards Py3K compatibility. |
|
|
|
(0034787)
|
|
David Gobbi
|
|
2015-07-16 11:11
|
|
|
|
|
(0034788)
|
|
hadimm
|
|
2015-07-16 12:00
|
|
|
Congrats David and thanks for the work ! |
|
|
|
(0034808)
|
|
David Gobbi
|
|
2015-07-20 11:07
|
|
Over the weekend, I fixed all the corner-cases in order to provide full backwards compatibility with the old wrappers. This means that I didn't have time for any actual Py3K code. Also, I made a new merge request, because the old one was becoming cluttered and hard to follow:
https://gitlab.kitware.com/vtk/vtk/merge_requests/436 [^]
One big change here is that VTK now has its own method descriptors, instead of using the PyMethodDescrObject. This is necessary in order to support methods where some signatures are static and others are not. |
|
|
|
(0035100)
|
|
Ben Boeckel (Kitware)
|
|
2015-08-28 18:17
|
|
|
Python3 support has landed in master. It will be available in 7.0. |
|