# I want Best Practices for Working With Python & Julia Together

**URL:** <https://discourse.julialang.org/t/i-want-best-practices-for-working-with-python-julia-together/131700>\
**Category:** New to Julia\
**Tags:** python\
**Created:** [August 19, 2025, 8:21am UTC](https://discourse.julialang.org/t/i-want-best-practices-for-working-with-python-julia-together/131700 "2025-08-19T08:21:16Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![stevengj](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stevengj/32/71_2.png) [@stevengj](https://discourse.julialang.org/u/stevengj)\
**Post date:** [August 19, 2025, 9:15pm UTC](https://discourse.julialang.org/t/i-want-best-practices-for-working-with-python-julia-together/131700/11 "2025-08-19T21:15:00Z")

</div>

> [@Alex1](#):
>
> Can you please explain shortly why PythonCall is better than PyCall?

See e.g. [[ANN] PythonCall and JuliaCall - #24 by stevengj](https://discourse.julialang.org/t/ann-pythoncall-and-juliacall/76778/24) — PythonCall has the advantage of coming later, and was able to re-visit some of the design decisions in PyCall.

---

_[View the full topic](https://discourse.julialang.org/t/i-want-best-practices-for-working-with-python-julia-together/131700)._