# Compile error rebuilding Slicer

**URL:** https://discourse.slicer.org/t/compile-error-rebuilding-slicer/6194
**Category:** Development
**Created:** [March 18, 2019, 7:33pm UTC](https://discourse.slicer.org/t/compile-error-rebuilding-slicer/6194 "2019-03-18T19:33:29Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![jamesobutler](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jamesobutler/32/7511_2.png) [@jamesobutler](https://discourse.slicer.org/u/jamesobutler)
#### Post date: [March 21, 2019, 6:30am UTC](https://discourse.slicer.org/t/compile-error-rebuilding-slicer/6194/6 "2019-03-21T06:30:10Z")

</div>

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](https://discourse.slicer.org/t/updating-slicer-to-work-with-python-3/4662/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](https://discourse.slicer.org/t/c-11-modernization-update-to-itk5-removal-of-obsolete-qt4-and-vtk7-support/6165) 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.

---

_[View the full topic](https://discourse.slicer.org/t/compile-error-rebuilding-slicer/6194)._