# IJulia build changing conda channel for some python packages within conda environment

**URL:** <https://discourse.julialang.org/t/ijulia-build-changing-conda-channel-for-some-python-packages-within-conda-environment/7665>\
**Category:** General Usage\
**Tags:** question\
**Created:** [December 10, 2017, 1:19am UTC](https://discourse.julialang.org/t/ijulia-build-changing-conda-channel-for-some-python-packages-within-conda-environment/7665 "2017-12-10T01:19:59Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Copper](https://avatars.discourse-cdn.com/v4/letter/c/dc4da7/32.png) [@Copper](https://discourse.julialang.org/u/Copper)\
**Post date:** [December 10, 2017, 1:19am UTC](https://discourse.julialang.org/t/ijulia-build-changing-conda-channel-for-some-python-packages-within-conda-environment/7665/1 "2017-12-10T01:19:59Z")

</div>

When building the IJulia package which is set up to make use of the Conda package and Anaconda most up to date Python 3 installation (with specific sub enviroment ‘conda\_jl’ I designated for Julia to be precise), some (8 out of 40 maybe) packages within the sub environment want to be updated through the ‘conda-forge’ channel ( **no change to the package version numbering whatsoever, only the channel reference** ).  
By the way ‘conda-forge’ channel’s priority for all conda environments is set to the bottom.  
IJulia works fine, however when I update the conda\_jl environment from time to time with ‘conda update’ the packages get a default update back to prioritized system channel.  
IJulia still works fine.  
Why would IJulia build process refer to ‘conda-forge’ channel for some packages and reinstall them?