# Merge Python and Julia, i.e. an (unofficial) integration proposal, sort of like the Mojo language

**URL:** https://discourse.julialang.org/t/merge-python-and-julia-i-e-an-unofficial-integration-proposal-sort-of-like-the-mojo-language/101844
**Category:** Community
**Created:** [July 20, 2023, 4:50pm UTC](https://discourse.julialang.org/t/merge-python-and-julia-i-e-an-unofficial-integration-proposal-sort-of-like-the-mojo-language/101844 "2023-07-20T16:50:22Z")
**Posts on this page:** 5
**Page:** 2

<div class="post-metadata">

### Author: ![tchebycheff](https://avatars.discourse-cdn.com/v4/letter/t/779978/32.png) [@tchebycheff](https://discourse.julialang.org/u/tchebycheff)
#### Post date: [October 12, 2023, 2:07am UTC](https://discourse.julialang.org/t/merge-python-and-julia-i-e-an-unofficial-integration-proposal-sort-of-like-the-mojo-language/101844/21 "2023-10-12T02:07:39Z")

</div>

For many programmers whose first high level language was C, anything without {} is jarring to read.

---

<div class="post-metadata">

### Author: ![xgdgsc](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/xgdgsc/32/608_2.png) [@xgdgsc](https://discourse.julialang.org/u/xgdgsc)
#### Post date: [October 12, 2023, 2:07am UTC](https://discourse.julialang.org/t/merge-python-and-julia-i-e-an-unofficial-integration-proposal-sort-of-like-the-mojo-language/101844/22 "2023-10-12T02:07:48Z")

</div>

Dot methods discovery is doable as [Feat/methodswith dot completion by xgdgsc · Pull Request #3240 · julia-vscode/julia-vscode · GitHub](https://github.com/julia-vscode/julia-vscode/pull/3240) . I’ ve used it just fine for months if you want to try at [Release A quick dot methods completion demo · xgdgsc/julia-vscode · GitHub](https://github.com/xgdgsc/julia-vscode/releases/tag/v1.41.1_methodswith) . I don’ t know why vscode devs seems not interested. They don’ t even have time for a simple [bugfix](https://github.com/julia-vscode/julia-vscode/pull/3139) and [translation](https://github.com/julia-vscode/julia-vscode/pull/3074).

---

<div class="post-metadata">

### Author: ![ParadaCarleton](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/paradacarleton/32/20005_2.png) [@ParadaCarleton](https://discourse.julialang.org/u/ParadaCarleton)
#### Post date: [October 12, 2023, 2:11am UTC](https://discourse.julialang.org/t/merge-python-and-julia-i-e-an-unofficial-integration-proposal-sort-of-like-the-mojo-language/101844/23 "2023-10-12T02:11:17Z")

</div>

> [@jlperla](#):
>
> but I don’t see any way that is true with auto-differentiation.

The static nature of Mojo should actually make that much easier. If you’re familiar with PyTorch or Jax, you’ll be familiar with a lot of the restrictions these force on you (no dispatch or runtime control flow, most notably). Mojo autodiff will probably be up and running within a few months if they get to work on it soon, because (unlike Julia) they can write the autodiff first, with restrictions, and only work on other code later. In Julia, autodiff typically tries to support general legacy code (arbitrary dispatch and control flow), which makes it obscenely difficult. (ReverseDiff doesn’t, but lacks tons of crucial features like GPU support.)

---

<div class="post-metadata">

### Author: ![ParadaCarleton](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/paradacarleton/32/20005_2.png) [@ParadaCarleton](https://discourse.julialang.org/u/ParadaCarleton)
#### Post date: [October 12, 2023, 2:21am UTC](https://discourse.julialang.org/t/merge-python-and-julia-i-e-an-unofficial-integration-proposal-sort-of-like-the-mojo-language/101844/24 "2023-10-12T02:21:15Z")

</div>

> [@xgdgsc](#):
>
> I don’ t know why vscode devs seems not interested. They don’ t even have time for a simple [bugfix](https://github.com/julia-vscode/julia-vscode/pull/3139) and [translation](https://github.com/julia-vscode/julia-vscode/pull/3074).

I’m sure they are, but they’re probably insanely busy. A lot of Julia packages are like that; it takes a lot longer to get PRs merged and reviewed in Julia than in other languages like Python, IME. Partly this is because of manpower issues, and partly because reviewing Julia PRs is a real slog sometimes; Julia provides very few tools for verifying correctness (no property-based testing, no static analysis, rampant mutability, no static shape-checking, no borrow checking…), and tons of performance footguns. Some correctness tools (e.g. StaticLint.jl) exist but aren’t widely used in CI, because there isn’t a single standardized CI script all users could use; many programmers don’t have time to learn about all the correctness checks they _could_ be adding to their code. So in Julia, you really have to read every line of code in detail, probably several times, since you can’t rely on tests to guarantee correctness.

---

<div class="post-metadata">

### Author: ![liuyxpp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/liuyxpp/32/9870_2.png) [@liuyxpp](https://discourse.julialang.org/u/liuyxpp)
#### Post date: [October 12, 2023, 3:25am UTC](https://discourse.julialang.org/t/merge-python-and-julia-i-e-an-unofficial-integration-proposal-sort-of-like-the-mojo-language/101844/25 "2023-10-12T03:25:50Z")

</div>

I am the opposite. My first high level language was C and I really hate `{}` and `;`. Because of this, when I first came across Python, I loved it. Now, I love Julia even more!

[Previous page](https://discourse.julialang.org/t/merge-python-and-julia-i-e-an-unofficial-integration-proposal-sort-of-like-the-mojo-language/101844.md?page=1)
