Re:PyO3: Rust Bindings for the Python Interpreter
by pansa2 on Friday January 29, 2021 @08:42AM
(#25957116)
How would PyO3 help you avoid type hints and mypy?
[ Parent
| on HN ]
Re:PyO3: Rust Bindings for the Python Interpreter
by brundolf on Friday January 29, 2021 @11:07AM
(#25958729)
I think the idea is that they move their business logic to the Rust code, since Rust's type system is more powerful and more sound, instead of trying to make do with MyPy
Re:PyO3: Rust Bindings for the Python Interpreter
by zerkten on Friday January 29, 2021 @01:22PM
(#25960520)
Wouldn't it be more of a priority to move it for lower memory use and higher request speed? A better type system is good, but often these are a struggle with scaling interpreted languages compared to other lower level languages.
Re:PyO3: Rust Bindings for the Python Interpreter
by brundolf on Friday January 29, 2021 @01:30PM
(#25960622)
For many people the primary appeal of Rust is its type system and related features (declaring deep immutability, pattern-matching, etc)
> often these are a struggle with scaling interpreted languages compared to other lower level languages
Not sure what's meant by this
Re:PyO3: Rust Bindings for the Python Interpreter
by LockAndLol on Friday January 29, 2021 @03:14PM
(#25961810)
It would minimize the python surface required to be covered with type-hints and mypy. If possible, one could simply point django to the modules generated from rust.
I'll give it a shot tonight and see how it goes. Now I'm curious.