Jean-Christophe Fillion-Robin

Since this issue hasn't been updated in years, I suggest we close it. Cc: @pieper @lassoan @nolden

Thanks for the report. > I suspect the culprit is the recent changes to the Python console Most likely. Would you have time to help address the issue ?

@saschazelzer This effort hasn't been completed because instead the support of component installation within CMake itself should be updated. More details here: http://public.kitware.com/Bug/view.php?id=14955 Since updating CMake itself may require more...

Since the can be of general use in the remaining of CTK (and also user code) I added them to `ctkMacro.h`. * We could also introduce a header named "ctkPythonQt.h"...

for reference, here is the email sent to the pythonqt discussion forum (not yet visible): ------- Hi Florian, Would you accept a patch like the following to systematically ignore old-style...

It turns out that (1) the patch was incorrect and (2) updating `PythonQtPythonInclude.h` by pushing/poping context is not working. Instead the following should be done: ```diff diff --git a/src/PythonQt.h b/src/PythonQt.h...

> my main objective is to get Slicer 4 build in Debian which requires CTK :+1: > At first these packages would include everything that is actually build Make sense...

Hi @gerddie Thanks for the reminder. As of today, we are working on having all Slicer specific changes upstream to VTK, same idea for ITK changes. Once this is complete...

This is not ready for integration yet. Further test would have to be done. I created the PR so that other could have a sneak peak. Ping @ntoussaint

@naucoin I added few comments in the reference commit.