# SlicerLeapMotionControl in Slicer 4.11.0

**URL:** <https://discourse.slicer.org/t/slicerleapmotioncontrol-in-slicer-4-11-0/6770>\
**Category:** Development\
**Created:** [May 13, 2019, 5:51am UTC](https://discourse.slicer.org/t/slicerleapmotioncontrol-in-slicer-4-11-0/6770 "2019-05-13T05:51:40Z")\
**Posts on this page:** 1\
**Showing post:** 10

<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:** [May 14, 2019, 4:29am UTC](https://discourse.slicer.org/t/slicerleapmotioncontrol-in-slicer-4-11-0/6770/10 "2019-05-14T04:29:45Z")

</div>

The next step would be to obtain the leap motion SDK for python 3.x.

Reading [https://developer.leapmotion.com/releases](https://developer.leapmotion.com/releases), it seems they have been removed from the latest SDK (Leap Motion Orion 4.0.0):

> Removed Leap.dll, all associated language bindings (LeapPython, LeapJava, Objective-C) and samples Leap Motion Orion 4.0.0

Now, reading the “Setting up a project” section found in the v3.2 of the documentation, we can find information about the python bindings:

- [https://developer-archive.leapmotion.com/documentation/python/index.html](https://developer-archive.leapmotion.com/documentation/python/index.html)
- [https://developer-archive.leapmotion.com/documentation/python/devguide/Project\_Setup.html](https://developer-archive.leapmotion.com/documentation/python/devguide/Project_Setup.html)

> The LeapPython library included in the Leap Motion SDK supports only Python 2.7. However, the SDK also includes the SWIG interface file used to generate the LeapPython source code, so advanced users can generate and compile their own version of LeapPython. For instructions, refer to [Generating a Python 3.3.0 Wrapper with SWIG 2.0.9](https://support.leapmotion.com/entries/39433657-Generating-a-Python-3-3-0-Wrapper-with-SWIG-2-0-9) in our support knowledge base.

If you download the v3.2 of the SDK and try to follow instruction from [https://support.leapmotion.com/hc/en-us/articles/223784048](https://support.leapmotion.com/hc/en-us/articles/223784048) , you should be able to address the remaining issues.

Also look like there are readily available code to make the python 3 binding for linux … see [GitHub - BlackLight/leap-sdk-python3: Leap Motion SDK - Python 3 module builder](https://github.com/BlackLight/leap-sdk-python3) but i couldn’t find a similar project.

Note that it may exist, i just didn’t spend too much time searching …

---

_[View the full topic](https://discourse.slicer.org/t/slicerleapmotioncontrol-in-slicer-4-11-0/6770)._