# Non-trivial conversions (Python to Julia)

**URL:** <https://discourse.julialang.org/t/non-trivial-conversions-python-to-julia/79665>\
**Category:** New to Julia\
**Tags:** quantum, optimization\
**Created:** [April 19, 2022, 12:20am UTC](https://discourse.julialang.org/t/non-trivial-conversions-python-to-julia/79665 "2022-04-19T00:20:43Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![Eben60](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/eben60/32/13475_2.png) [@Eben60](https://discourse.julialang.org/u/Eben60)\
**Post date:** [April 19, 2022, 1:07pm UTC](https://discourse.julialang.org/t/non-trivial-conversions-python-to-julia/79665/8 "2022-04-19T13:07:29Z")

</div>

> [@Workflow for converting Python scripts](https://discourse.julialang.org/t/workflow-for-converting-python-scripts/32737/3):
>
> My recipe for converting from one language to another is quite simple, at least when the second language is able to fully wrap the first one, which is the case for Julia thanks to PyCall. This is what I usually do when I go from Python -\> Julia: Create a script/workflow which you want to port to Julia, this can be something easy like calling a function, or more complex, like full analysis chain. Smaller steps are easier though. Write unit tests and/or high level tests in Julia to have an autom…

---

_[View the full topic](https://discourse.julialang.org/t/non-trivial-conversions-python-to-julia/79665)._
