You're reading from Mastering Python 2E Write powerful and efficient code using the full range of Python's capabilities

Product type Paperback

Published in May 2022

Last Updated in May 2022

Publisher Packt

ISBN-13 9781800207721

Length 710 pages

Edition 2nd Edition

Languages

Python

Tools

Dask

Concepts

Programming Language

Author (1):

Rick Hattem

View More author details

Table of Contents (21) Chapters

Preface

1. Getting Started – One Environment per Project FREE CHAPTER

2. Interactive Python Interpreters

3. Pythonic Syntax and Common Pitfalls

4. Pythonic Design Patterns

5. Functional Programming – Readability Versus Brevity

6. Decorators – Enabling Code Reuse by Decorating

7. Generators and Coroutines – Infinity, One Step at a Time

8. Metaclasses – Making Classes (Not Instances) Smarter

9. Documentation – How to Use Sphinx and reStructuredText

10. Testing and Logging – Preparing for Bugs

11. Debugging – Solving the Bugs

12. Performance – Tracking and Reducing Your Memory and CPU Usage

13. asyncio – Multithreading without Threads

14. Multiprocessing – When a Single CPU Core Is Not Enough

15. Scientific Python and Plotting

16. Artificial Intelligence

17. Extensions in C/C++, System Calls, and C/C++ Libraries

18. Packaging – Creating Your Own Libraries or Applications

19. Other Books You May Enjoy

20. Index

Introduction to packages

Python has a very messy history when it comes to packaging. Over the decades that Python has existed, we have (had) libraries such as distutils, distutils2, distribute, buildout, setuptools, packaging, distlib, poetry, and several others. All of these projects were started with the best intentions to improve upon the status quo, unfortunately with varying degrees of success. And that is not to mention all the different package types such as wheels, source packages, and binary packages such as eggs, Red Hat .rpm files, and Windows .exe/.msi files.

The good news is that even though packaging has had a complicated history, things have started to settle over the last few years and the situation has improved greatly. Building packages has become much easier, and maintaining a stable project dependency state is now easily possible.