Comment on Compiling typed Python: types are very broad hints and they are sometimes lies.

A_A@lemmy.world ⁨1⁩ ⁨year⁩ ago

• Moc@lemmy.world ⁨1⁩ ⁨year⁩ ago

  Python and Rust apparently pair nicely

  source

  • UlrikHD@programming.dev ⁨1⁩ ⁨year⁩ ago

    Could you elaborate on that point? Is it as smooth as using C?

    source

    • Turun@feddit.de ⁨1⁩ ⁨year⁩ ago

      I never used C, so I don’t know how easy it is there.

      In rust there is a library that takes care of all the details (PyO3), so you only need to add #[pyclass] or #[pymethod] above your structs and methods, define what the module/submodule/classes/functions is and run the tool provided by the PyO3 library to compile the code and install it in a local virtual environment.

      So it’s literally (the actual meaning of literally) just two lines for every class or method you want to have available in python and ten lines in the Cargo.toml/pyproject.toml config files.

      This article shows the basic usage.

      source

      • UlrikHD@programming.dev ⁨1⁩ ⁨year⁩ ago

        Interesting stuff, might give me an excuse to look into rust in the future. Thanks!

        source

        • -> View More Comments
    • Moc@lemmy.world ⁨1⁩ ⁨year⁩ ago

      Rust compiles to bytecode like C.

      Just like you can call binaries written in C from Python and return their result, you can also run binaries written in Rust. In fact, there are helper libraries to provide some syntax to do this.

      source

      • UlrikHD@programming.dev ⁨1⁩ ⁨year⁩ ago

        I assume you meant that both Rust and C compiles into machine code? Python compiles into bytecode that is then run in a VM, Rust and C usually doesn’t do that as far as I know.

        I was mostly curious if it was as easy as in C. Turun’s reply answered that question though. Cheers.

        source