# Binder getting stuck while installing conda's environment.yml

**URL:** <https://discourse.jupyter.org/t/binder-getting-stuck-while-installing-condas-environment-yml/8680>\
**Category:** repo help\
**Created:** [April 8, 2021, 4:34am UTC](https://discourse.jupyter.org/t/binder-getting-stuck-while-installing-condas-environment-yml/8680 "2021-04-08T04:34:03Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![fomightez](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.jupyter.org/fomightez/32/495_2.png) [@fomightez](https://discourse.jupyter.org/u/fomightez)\
**Post date:** [April 8, 2021, 4:34pm UTC](https://discourse.jupyter.org/t/binder-getting-stuck-while-installing-condas-environment-yml/8680/3 "2021-04-08T16:34:28Z")

</div>

A couple of things to try in addition to or before trying a local build…

One simple idea to try would be to include `pip` as a dependency. For several months I had been seeing it in the MyBinder build stream noted that something was saying soon including `pip` as a dependency is required. So I started including it a while ago in new or updated `environment.yml`. I note that yours doesn’t have it.

See an example here:

> <https://github.com/fomightez/cl_sq_demo-binder/blob/cf53e363902d2457155b3ad49484ea8d1fe2d207/environment.yml>

You have a complex set of requirements in your `environment.yml` and then you specify an old version of Python. Sometimes mixing pinning and unpinning is a bad idea. So a related idea would be to listing pip earlier and also unpinning everything in a simpler, separate repo and then build back up to see where breaks.

---

_[View the full topic](https://discourse.jupyter.org/t/binder-getting-stuck-while-installing-condas-environment-yml/8680)._