In Python applications, logging module should be used instead of print() to build a log system with clear structure, complete information and easy to troubleshoot problems. First, use the standard library logging instead of print() because it supports multi-level logging (DEBUG, INFO, WARNING, ERROR, CRITICAL) and can flexibly control the output format and location; second, context information, such as module name, function name, line number and key variable values, should be added to the log to improve the readability and diagnostic capabilities of the log; third, process logs according to the environment, enable the DEBUG level during development, and the production environment is limited to I. NFO or WARNING or above levels, and logs can be centrally managed in combination with files or third-party services; finally, common pitfalls need to be avoided, such as using logging.exception() instead of print(e), and not calling basicConfig() at the top level of the module. It is recommended to use __name__ to create loggers, and use RotatingFileHandler to implement log rotation, thereby ensuring the efficiency and practicality of the log system.
Logging in Python applications seems simple, but if you really do it well, you still have to pay attention to the method. Just writing print()
is not enough. What is really useful is a log system with clear structure, complete information and easy to troubleshoot problems. The following points are practical practices I summarized in actual projects.

Use standard library logging instead of print
Many newbies like to use print()
to output debugging information at the beginning, but in formal projects, this is far from enough. Python's built-in logging
module not only supports different levels of logging (such as DEBUG, INFO, WARNING, ERROR, CRITICAL), but also provides flexible control of output location and format.

For example:
import logging logging.basicConfig(level=logging.INFO) logger = logging.getLogger(__name__) logger.info("This is an info message") logger.error("This is an error message")
This way you can only display logs at ERROR or above level as needed without INFO disrupting your vision. And it supports output to files, mail, and even remote servers.

Add context information to the log
It doesn’t help much just looking at a “wrong”. The key is to know where and why it went wrong. So suggestion:
- Each log contains information such as module name, function name, line number, etc.
- Record key variable values ??or input parameters
- If it is in a web application, you can add the request path, user ID, etc.
The configuration method is also very simple. Add format parameters to basicConfig:
logging.basicConfig( format="%(asctime)s [%(levelname)s] %(name)s - %(funcName)s:%(lineno)d - %(message)s", level=logging.DEBUG )
This way the output logs are clearer.
Graded processing log: Development vs. Production
During local development, we can open DEBUG-level logs to facilitate viewing details; but in production environments, only INFO or WARNING or above logs are usually retained to avoid performance loss and log explosion.
You can dynamically set log levels according to different environments, such as:
if ENV == "production": logger.setLevel(logging.WARNING) else: logger.setLevel(logging.DEBUG)
You can also write logs to different files, or centrally managed through third-party services (such as Sentry, ELK Stack).
Avoid common pitfalls
When using logging, there are several common minor problems that are easily overlooked:
- ? Do not use
except Exception as e: print(e)
,logging.exception()
should be used to print the complete error stack - ? Do not call
basicConfig()
directly at the top of the module, otherwise it may affect the log configuration of other modules. - ? It is recommended to use
__name__
to create a logger to ensure that each module has an independent namespace - ? It is best to rotate log files regularly, you can use
RotatingFileHandler
orTimedRotatingFileHandler
Basically that's it. The log system is not complicated, but the details are not done properly, and it can easily become a decoration or burden. Only by rational configuration and standardized use can we help at critical moments.
The above is the detailed content of Best Practices for Logging in Python Applications. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

Python's unittest and pytest are two widely used testing frameworks that simplify the writing, organizing and running of automated tests. 1. Both support automatic discovery of test cases and provide a clear test structure: unittest defines tests by inheriting the TestCase class and starting with test\_; pytest is more concise, just need a function starting with test\_. 2. They all have built-in assertion support: unittest provides assertEqual, assertTrue and other methods, while pytest uses an enhanced assert statement to automatically display the failure details. 3. All have mechanisms for handling test preparation and cleaning: un

PythonisidealfordataanalysisduetoNumPyandPandas.1)NumPyexcelsatnumericalcomputationswithfast,multi-dimensionalarraysandvectorizedoperationslikenp.sqrt().2)PandashandlesstructureddatawithSeriesandDataFrames,supportingtaskslikeloading,cleaning,filterin

Dynamic programming (DP) optimizes the solution process by breaking down complex problems into simpler subproblems and storing their results to avoid repeated calculations. There are two main methods: 1. Top-down (memorization): recursively decompose the problem and use cache to store intermediate results; 2. Bottom-up (table): Iteratively build solutions from the basic situation. Suitable for scenarios where maximum/minimum values, optimal solutions or overlapping subproblems are required, such as Fibonacci sequences, backpacking problems, etc. In Python, it can be implemented through decorators or arrays, and attention should be paid to identifying recursive relationships, defining the benchmark situation, and optimizing the complexity of space.

To implement a custom iterator, you need to define the __iter__ and __next__ methods in the class. ① The __iter__ method returns the iterator object itself, usually self, to be compatible with iterative environments such as for loops; ② The __next__ method controls the value of each iteration, returns the next element in the sequence, and when there are no more items, StopIteration exception should be thrown; ③ The status must be tracked correctly and the termination conditions must be set to avoid infinite loops; ④ Complex logic such as file line filtering, and pay attention to resource cleaning and memory management; ⑤ For simple logic, you can consider using the generator function yield instead, but you need to choose a suitable method based on the specific scenario.

Future trends in Python include performance optimization, stronger type prompts, the rise of alternative runtimes, and the continued growth of the AI/ML field. First, CPython continues to optimize, improving performance through faster startup time, function call optimization and proposed integer operations; second, type prompts are deeply integrated into languages ??and toolchains to enhance code security and development experience; third, alternative runtimes such as PyScript and Nuitka provide new functions and performance advantages; finally, the fields of AI and data science continue to expand, and emerging libraries promote more efficient development and integration. These trends indicate that Python is constantly adapting to technological changes and maintaining its leading position.

Python's socket module is the basis of network programming, providing low-level network communication functions, suitable for building client and server applications. To set up a basic TCP server, you need to use socket.socket() to create objects, bind addresses and ports, call .listen() to listen for connections, and accept client connections through .accept(). To build a TCP client, you need to create a socket object and call .connect() to connect to the server, then use .sendall() to send data and .recv() to receive responses. To handle multiple clients, you can use 1. Threads: start a new thread every time you connect; 2. Asynchronous I/O: For example, the asyncio library can achieve non-blocking communication. Things to note

The core answer to Python list slicing is to master the [start:end:step] syntax and understand its behavior. 1. The basic format of list slicing is list[start:end:step], where start is the starting index (included), end is the end index (not included), and step is the step size; 2. Omit start by default start from 0, omit end by default to the end, omit step by default to 1; 3. Use my_list[:n] to get the first n items, and use my_list[-n:] to get the last n items; 4. Use step to skip elements, such as my_list[::2] to get even digits, and negative step values ??can invert the list; 5. Common misunderstandings include the end index not

Polymorphism is a core concept in Python object-oriented programming, referring to "one interface, multiple implementations", allowing for unified processing of different types of objects. 1. Polymorphism is implemented through method rewriting. Subclasses can redefine parent class methods. For example, the spoke() method of Animal class has different implementations in Dog and Cat subclasses. 2. The practical uses of polymorphism include simplifying the code structure and enhancing scalability, such as calling the draw() method uniformly in the graphical drawing program, or handling the common behavior of different characters in game development. 3. Python implementation polymorphism needs to satisfy: the parent class defines a method, and the child class overrides the method, but does not require inheritance of the same parent class. As long as the object implements the same method, this is called the "duck type". 4. Things to note include the maintenance
