Book Image

Modern Python Cookbook

Book Image

Modern Python Cookbook

Overview of this book

Python is the preferred choice of developers, engineers, data scientists, and hobbyists everywhere. It is a great scripting language that can power your applications and provide great speed, safety, and scalability. By exposing Python as a series of simple recipes, you can gain insight into specific language features in a particular context. Having a tangible context helps make the language or standard library feature easier to understand. This book comes with over 100 recipes on the latest version of Python. The recipes will benefit everyone ranging from beginner to an expert. The book is broken down into 13 chapters that build from simple language concepts to more complex applications of the language. The recipes will touch upon all the necessary Python concepts related to data structures, OOP, functional programming, as well as statistical programming. You will get acquainted with the nuances of Python syntax and how to effectively use the advantages that it offers. You will end the book equipped with the knowledge of testing, web services, and configuration and application integration tips and tricks. The recipes take a problem-solution approach to resolve issues commonly faced by Python programmers across the globe. You will be armed with the knowledge of creating applications with flexible logging, powerful configuration, and command-line options, automated unit tests, and good documentation.
Table of Contents (18 chapters)
Title Page
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Managing arguments and configuration in composite applications


When we have a complex suite (or system) of individual applications, it's common for several applications to share common features. We can, of course, use ordinary inheritance to define a library module that provides the common classes and functions to each of the individual applications in a complex suite.

The downside of creating a number of separate applications is that the external CLI is tied directly to the software architecture. It becomes awkward to rearrange the software components because changes will also alter the visible CLI.

The coordination of common features among many application files can become awkward. For example, defining the various, one-letter abbreviated options for command-line arguments is difficult. It requires keeping some kind of master list of options, outside all of the individual application files. It seems like this should be kept in one place in the code somewhere.

Is there an alternative to inheritance...