python3.8.tar.gz

Python3.8

Python3.8Code

This course is an invaluable resource for anyone who wants to learn the correct Pythonian way of writing highly performant code that is easy to maintain and grow.

The course is divided into six chapters: documentation tips, data types/data structures tips, safety tips, performance tips, function design tips, and general tips. Throughout each chapter, you will get hands-on experience working with real Python code to help ingrain each concept.

By the end, you will know how to make your programs correct, safe, fast, and easy to maintain.

Pythonic Programming Tips for Software Engineers

## Let `input()` speak for itself

There are many questions we must ask when a console-based program suddenly stops. Why? Did it hang up? Is it busy? Is it waiting for the input? If so, for what is it waiting? As a programmer, we can eliminate most of these questions by providing **prompts**.

A prompt is a printed invitation to enter some missing information. We should display a prompt just before the program stops and wait for user input (presumably by calling the `input()` function). The prompt should explain concisely, in a language suitable to the expected user, what the user should input and how. It is customary, but not required, for a prompt to end with a colon and space.

We can use the `print()` function to display the prompt, followed by `input()` to collect the input. A better solution is to let `input()` speak for itself; if we pass an argument to `input()`, the argument will be printed just before the function stops:
```python
year = input('Enter year of birth: ')
```
Keeping the prompt and the collector together self-documents the collector’s purpose and reminds the user of which input is expected, especially if the program requires more than one input.

> Remember that the prompt is merely a string. It can be a constant and can be pre-calculated. It can also be calculated during the call to personalize the invitation or configure it in any other way:
```python
name = input('Enter your name: ').strip()
year = input(f'What is your year of birth, {name}? ')
```



# Let `input()` speak for itself

There are many questions we must ask when a console-based program suddenly stops. Why? Did it hang up? Is it busy? Is it waiting for the input? If so, for what is it waiting? As a programmer, we can eliminate most of these questions by providing **prompts**.

A prompt is a printed invitation to enter some missing information. We should display a prompt just before the program stops and wait for user input (presumably by calling the `input()` function). The prompt should explain concisely, in a language suitable to the expected user, what the user should input and how. It is customary, but not required, for a prompt to end with a colon and space.

We can use the `print()` function to display the prompt, followed by `input()` to collect the input. A better solution is to let `input()` speak for itself; if we pass an argument to `input()`, the argument will be printed just before the function stops:
```python
year = input('Enter year of birth: ')
```
Keeping the prompt and the collector together self-documents the collector’s purpose and reminds the user of which input is expected, especially if the program requires more than one input.

> Remember that the prompt is merely a string. It can be a constant and can be pre-calculated. It can also be calculated during the call to personalize the invitation or configure it in any other way:
```python
name = input('Enter your name: ').strip()
year = input(f'What is your year of birth, {name}? ')
```



Learn how to prompt input, use dummy variables, and enum in this lesson.

Introduction

Documentation Tips

General Tips

Data Types and Data Structures Tips

Function Tips

Performance Tips

Safety Tips

Wrapping Up

Input, Variables, and Enumeration Related Tips

Let `input()` speak for itself