# Looking for feedback - minimal repo that calls Julia code from Python

**URL:** <https://discourse.julialang.org/t/looking-for-feedback-minimal-repo-that-calls-julia-code-from-python/109571>\
**Category:** New to Julia\
**Created:** [February 1, 2024, 1:09pm UTC](https://discourse.julialang.org/t/looking-for-feedback-minimal-repo-that-calls-julia-code-from-python/109571 "2024-02-01T13:09:44Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![aramend](https://avatars.discourse-cdn.com/v4/letter/a/a88e57/32.png) [@aramend](https://discourse.julialang.org/u/aramend)\
**Post date:** [February 1, 2024, 1:09pm UTC](https://discourse.julialang.org/t/looking-for-feedback-minimal-repo-that-calls-julia-code-from-python/109571/1 "2024-02-01T13:09:44Z")

</div>

Hi all!

I have created a minimal [repository](https://github.com/jkasak/juliapy-interop-example) where a Python API function calls an underlying Julia function and returns the computed result in Python land. If you want to try it, `make run` should work for you on linux or macos.

This is for a scenario where both core development of Julia software and maintenance of a Python API live in one monorepo.

I’ll also copy the folder structure here, for a quick overview.

```julia
.
├── demo_data.json
├── demo_script.py
├── julia_src
│ └── MyJuliaModule.jl
├── Makefile
├── Project.toml
├── python_src
│ ├── __init__.py
│ ├── _julia_backend.py
│ └── _python_api.py
├── README.md
└── requirements.txt

```

Briefly:

- Is `juliacall` the appropriate Python library to use?
- Do the folder structure and contents of `python_src/_julia_backend.py` look sane?
- If you were in my shoes, what would you do differently?

PS. Providing only a link to the repo seemed appropriate here. Please inform me if any more information is needed.