# Updating slicer to work with python 3

**URL:** https://discourse.slicer.org/t/updating-slicer-to-work-with-python-3/4662
**Category:** Development
**Tags:** build
**Created:** [November 6, 2018, 7:31pm UTC](https://discourse.slicer.org/t/updating-slicer-to-work-with-python-3/4662 "2018-11-06T19:31:37Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)
#### Post date: [March 16, 2019, 8:17pm UTC](https://discourse.slicer.org/t/updating-slicer-to-work-with-python-3/4662/3 "2019-03-16T20:17:40Z")

</div>

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

> <https://github.com/Slicer/Slicer/issues/1118>
>
> \_This issue was created automatically from an original \[Mantis Issue\](https://ma…ntisarchive.slicer.org/view.php?id=1118). Further discussion may take place here.\_

Cc: @bpaniagua @Andinet_Enquobahrie

---

_[View the full topic](https://discourse.slicer.org/t/updating-slicer-to-work-with-python-3/4662)._