# Julia-Python interface fails in Julia library likely due to wrong SSL credentials

**URL:** https://discourse.julialang.org/t/julia-python-interface-fails-in-julia-library-likely-due-to-wrong-ssl-credentials/121675
**Category:** General Usage
**Tags:** pycall, github-actions, pythoncall
**Created:** [October 24, 2024, 12:45am UTC](https://discourse.julialang.org/t/julia-python-interface-fails-in-julia-library-likely-due-to-wrong-ssl-credentials/121675 "2024-10-24T00:45:49Z")
**Posts on this page:** 1
**Showing post:** 11

<div class="post-metadata">

### Author: ![mrufsvold](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mrufsvold/32/31600_2.png) [@mrufsvold](https://discourse.julialang.org/u/mrufsvold)
#### Post date: [October 31, 2024, 12:19pm UTC](https://discourse.julialang.org/t/julia-python-interface-fails-in-julia-library-likely-due-to-wrong-ssl-credentials/121675/11 "2024-10-31T12:19:03Z")

</div>

There are lots of threads in this conversation, so I’m sorry to pull focus from the python installation issue, but I just saw this comment about Python+Julia+OpenSSL that might be of interest.

> [@Recommand \`curl | bash\` as default installation is not ideal?](https://discourse.julialang.org/t/recommand-curl-bash-as-default-installation-is-not-ideal/121820/8):
>
> Ah, maybe it’s purely a package problem then. But if you load the JLL OpenSSL before the Python one in a session with PythonCall, and the two versions are not the same, Python will not be able to successfully call into OpenSSL. (There’s a fix for this in CondaPkg.jl for this exact reason). I guess the problem is getting Pkg info to Conda, from the Conda end…(since the Julia/Pkg end is solved via CondaPkg!) A bigger problem is coordinating JLL versions between different packages, since Julia …

---

_[View the full topic](https://discourse.julialang.org/t/julia-python-interface-fails-in-julia-library-likely-due-to-wrong-ssl-credentials/121675)._