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

Answers

  1. Our docstrings can support Markdown while we are building our structs and functions. Because it's Markdown, we can document ways in which we can implement the struct or function. If we are using Visual Studio Code, this also helps our productivity, as merely hovering the mouse over the function or struct throws up the documentation.
  2. Keeping our modules constrained to a single concept increases the flexibility of the application, enabling us to chop and change modules as and when they are needed.
  3. In order to keep our modules isolated, we need to keep the interfaces of the module the same; this means that we can change logic inside the module without having to alter anything in the rest of the application. If we delete the module, we only have to look for implementations of the interface throughout the application as opposed to the implementation of all functions and structs in the module.
  4. We manage our dependencies in the Cargo.toml file. Just running Cargo...