# Creating an package (and eventually app) with Python dependencies

**URL:** <https://discourse.julialang.org/t/creating-an-package-and-eventually-app-with-python-dependencies/107317>\
**Category:** New to Julia\
**Tags:** package, pycall, pythoncall\
**Created:** [December 8, 2023, 6:03am UTC](https://discourse.julialang.org/t/creating-an-package-and-eventually-app-with-python-dependencies/107317 "2023-12-08T06:03:22Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Palli](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/palli/32/3380_2.png) [@Palli](https://discourse.julialang.org/u/Palli)\
**Post date:** [December 8, 2023, 4:34pm UTC](https://discourse.julialang.org/t/creating-an-package-and-eventually-app-with-python-dependencies/107317/4 "2023-12-08T16:34:20Z")

</div>

I haven’t used together myself, just know about the issue and solution in the doc (why I wrote read carefully, didn’t it work?):

> - To force PythonCall to use the same Python interpreter as PyCall, set the environment variable `JULIA_PYTHONCALL_EXE` to `"@PyCall"`. Note that this will opt out of automatic dependency management using CondaPkg.
> - Alternatively, to force PyCall to use the same interpreter as PythonCall, set the environment variable `PYTHON` to `PythonCall.C.CTX.exe_path` and then `Pkg.build("PyCall")`. You will need to do this each time you change project, because PythonCall by default uses a different Python for each project.

---

_[View the full topic](https://discourse.julialang.org/t/creating-an-package-and-eventually-app-with-python-dependencies/107317)._