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

Questions

  1. Why can we not simply copy a String?
  2. Rust has strong typing. In which two ways can we enable a container such as a vector or hashmap to contain multiple different types?
  3. How are Python decorators and Rust macros the same?
  4. What is the Python equivalent to a main function in Rust?
  5. Why can we get a higher integer value with the same number of bytes with an unsigned integer than a signed integer?
  6. Why do we have to be strict with lifetimes and scopes when coding in Rust?
  7. Can we reference a variable when it has been moved?
  8. What can you do to an original variable if it is currently being borrowed in an immutable state?
  9. What can you do to an original variable if it is currently being borrowed in a mutable state?