Compile error rebuilding Slicer

[jamesobutler (James Butler)]

If the fix that worked for you was updating Slicer’s python from 2.7.13 to a version that is <3.0 and >=2.7.15 that is great to hear.

Work is scheduled to move Slicer to python 3 and this is happening starting this Monday. See

Updating slicer to work with python 3

This past week, we were busy modernizing the Slicer code base. See C++11 modernization, update to ITK5, removal of obsolete Qt4 and VTK7 support This delayed the transition to Python 3. The associated effort will be resumed on March 25th. In the mean time, here is a work-in-progress topic based on some preliminary work from @ihnorton Cc: @bpaniagua @Andinet_Enquobahrie

It seems like python 3.6.5 and later also has the fix. So the transition to python 3 next week will be the likely path to how the issue will be resolved in Slicer.