# Need slicer 4.5.0-2016-06-22 package for MacOs (nighly build)

**URL:** <https://discourse.slicer.org/t/need-slicer-4-5-0-2016-06-22-package-for-macos-nighly-build/621>\
**Category:** Support\
**Created:** [July 4, 2017, 11:08am UTC](https://discourse.slicer.org/t/need-slicer-4-5-0-2016-06-22-package-for-macos-nighly-build/621 "2017-07-04T11:08:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![florianputz](https://avatars.discourse-cdn.com/v4/letter/f/a3d4f5/32.png) [@florianputz](https://discourse.slicer.org/u/florianputz)\
**Post date:** [July 4, 2017, 11:08am UTC](https://discourse.slicer.org/t/need-slicer-4-5-0-2016-06-22-package-for-macos-nighly-build/621/1 "2017-07-04T11:08:42Z")

</div>

Hello everyone,

we developed an internal segmentation solution (python module) for **Slicer 4.5-2016-06-22** (Windows version, nightly build).

Everything worked quite fine.

Now, the module is planned to be used on a macOs device.

Unfortunately, **Slicer 4.5-2016-06-22 nighly build isn’t available anymore for download**  
and [http://slicer.kitware.com/midas3/download/item/244951](http://slicer.kitware.com/midas3/download/item/244951) etc. always gives a “ **Unable to find file on the disk** ”-error.

Sadly, there are quite a few errors, when running the python module on later or earlier stable versions of 3DSlicer.

The Slicer 4.5-2016-06-22 nighly package thus would save us quite some time in rewriting the code and testing.

Any help is greatly appreciated.

Thank you

Florian

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [July 4, 2017, 4:07pm UTC](https://discourse.slicer.org/t/need-slicer-4-5-0-2016-06-22-package-for-macos-nighly-build/621/2 "2017-07-04T16:07:03Z")

</div>

We don’t archive all nightly build versions of indefinitely long. I would recommend to update to the latest nightly version. Required changes should be all trivial. Just write what errors you get and we can tell what to change.