Hello ! I’m Xavier Jouvenot and in this small post, I am going to explain how to automatically check if your python code is well formatted with Azure Pipelines.
Self promotion: Here are a few social networks where you can follow me and check my work as a programmer and a writer 😉
Today, we are going to focus on how we can automatically check if the python code you are versioning is well formatted, and more specifically, how you can use Azure Pipelines to do so. To automate this process will make your team more efficient and the code more consistent since everyone will have to be on board and format their code each time they want to contribute.
If you are not convinced that you should format you code, I really encourage you to go look at the previous article I did on Formatting and Automation, where I go in detail on why you should definitively format your code, and do it in a automatic way, to make your code more readable and make your team more productive since they won’t have to spend time arguing about Spaces VS Tabs.
The short answer, for the people who don’t want to read through the entire article (I know you do that! I do it too 😆) is to insert the following steps in your Azure Pipelines process:
- script: | pip3 install black displayName: Installs the latest version of black - script: | black --check . displayName: Checks if the python scripts are formatted properly with black
If you have my previous article about "Formatting Python – Why and How !", you may already know about about the tool named black. For those who don’t know, this is a code formatter, described by its authors as follow: > Black is the uncompromising Python code formatter. By using it, you agree to cede control over minutiae of hand-formatting. In return, Black gives you speed, determinism, and freedom from pycodestyle nagging about formatting. You will save time and mental energy for more important matters.
In the steps above, I start by installing this tool with the python package manager pip. Then, I run
black at the root of the folder, meaning that it is going to find all the Python files in repository and, since we are using the flag
--check, verify if they are well formatted. If one Python file is not formatted correctly, then, the black command will return an error, and the corresponding step in Azure Pipelines will fail.
If you want, you can specify directly the list of the Python files, instead of letting the tool scan through all the repository recursively. 😉
Finally, it is interesting to notice that those steps can be uses on any environment available in Azure Pipelines. I actually made a GitHub repository in which I setup Azure Pipelines to run the steps described before on every environment available. You can take a look here as I will update it when new environment will be available on Azure Pipelines 😉
Thank you all for reading this article, And until my next article, have a splendid day 😉