# Pip in nightly build not working

**URL:** <https://discourse.slicer.org/t/pip-in-nightly-build-not-working/3325>\
**Category:** Development\
**Tags:** python, pip\
**Created:** [June 28, 2018, 12:41pm UTC](https://discourse.slicer.org/t/pip-in-nightly-build-not-working/3325 "2018-06-28T12:41:57Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![ihnorton](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/ihnorton/32/9_2.png) [@ihnorton](https://discourse.slicer.org/u/ihnorton)\
**Post date:** [July 2, 2018, 3:21pm UTC](https://discourse.slicer.org/t/pip-in-nightly-build-not-working/3325/5 "2018-07-02T15:21:03Z")

</div>

> [@lassoan](#):
>
> Would it make sense to add Slicer launcher application shortcut for pip? Pip could then launched as: Slicer.exe --pip install…

I think `Slicer --launch` already prefers binaries in Slicer’s PATH, so the other option is to document pip as `Slicer --launch pip` (only a few more characters).

---

_[View the full topic](https://discourse.slicer.org/t/pip-in-nightly-build-not-working/3325)._