#63: Logging in Flask
After last week's first steps with logging, it is now time to add logging to our Flask application.
After last week's first steps with logging, it is now time to add logging to our Flask application.
Logging allows us to understand what is going on inside our applications. Luckily for us, Python comes with a developer-friendly logger that works without much set-up code.
Python is not the fastest programming language, but sometimes your code may still run too fast. Let us look how we can tell Python to take a break.
If you get bored by the dots in the pytest test-runner you may be interested in the pytest-sugar plugin. Let us look what it does and how you can get it.
A good illustration of source code is a must-have when you want to use MkDocs for your project documentation. Let us find out what we need to display code snippets.
Last week I started an introduction to MkDocs. In this post we change the theme and look at other ways to customise our MkDocs site.
MkDocs is a so-called static site generator that uses Python to turn your Markdown files into HTML. It is a great tool to document your projects and works nicely with GitHub Pages.
The more I work with pytest, the more I like the flexibility it offers. Today I post about 3 command-line options that help me a lot and are easy to overlook.
We need pytest and other dependencies only while we develop our application, but not when we run them in production. Is there a way that allows us to track the dependencies but not install all of them all the time?
The test summary of pytest is good when you develop your application. But when you want to share these results with others, the lack of details is a problem. Let us look how we can create a more detailed report that we can share.