Book Image

Speed Up Your Python with Rust

By : Maxwell Flitton
5 (2)
Book Image

Speed Up Your Python with Rust

5 (2)
By: Maxwell Flitton

Overview of this book

Python has made software development easier, but it falls short in several areas including memory management that lead to poor performance and security. Rust, on the other hand, provides memory safety without using a garbage collector, which means that with its low memory footprint, you can build high-performant and secure apps relatively easily. However, rewriting everything in Rust can be expensive and risky as there might not be package support in Rust for the problem being solved. This is where Python bindings and pip come in. This book will help you, as a Python developer, to start using Rust in your Python projects without having to manage a separate Rust server or application. Seeing as you'll already understand concepts like functions and loops, this book covers the quirks of Rust such as memory management to code Rust in a productive and structured manner. You'll explore the PyO3 crate to fuse Rust code with Python, learn how to package your fused Rust code in a pip package, and then deploy a Python Flask application in Docker that uses a private Rust pip module. Finally, you'll get to grips with advanced Rust binding topics such as inspecting Python objects and modules in Rust. By the end of this Rust book, you'll be able to develop safe and high-performant applications with better concurrency support.
Table of Contents (16 chapters)
1
Section 1: Getting to Understand Rust
5
Section 2: Fusing Rust with Python
11
Section 3: Infusing Rust into a Web Application

Deploying Rust nightly in Flask

To package our nightly database Rust package so that it can be deployed, we have to add another clone of our GitHub repository to our build Bash script, install nightly, and switch to it when we are installing our database package with pip. You can probably guess what we are going to achieve by cloning our database GitHub repository in our Bash script.

For reference, our src/build_image.sh file will take the form of the following code:

. . .
git clone https://github.com/maxwellflitton/
flitton-fib-rs.git
git clone https://github.com/maxwellflitton/
rust-db-cloning.git
rm -rf ./flitton-fib-rs/.git
rm -rf ./rust-db-cloning/.git
docker build . --no-cache -t flask-fib
rm -rf ./flitton-fib-rs
rm -rf ./rust-db-cloning

Here, we can see that we have merely added the code for cloning the rust-db-cloning repository, removed the .git file in that rust-db-cloning repository, and then removed the rust-db-cloning repository once the image build has finished...