1.
Automate cleaning
code in few easy
steps!
Ester Beltrami
Twitter: @esterbeltrami
GitHub: github.com/estyxx

2.
Ester
•PyCon Italia
organizer
•Strawberry-graphql
core-dev
•Poetry Package
manager contributor

3.
We write some code

4.
We push the code

5.
Time to relax and wait

6.
We came back to the
pipeline and…

7.
pre-commit

8.
.yaml file config

9.
Some nice hooks to include!
• pyupgrade to automatically upgrade syntax for newer
versions
• flake8-eradicate to find commented out (or so called "dead")
code
• autoflake to removes unused imports and unused variables

10.
not only code quality, also security!

11.
What are the benefits?

12.
Identify issues
*before* the
code review

13.
It’s not all
about
python…

14.
Why developers don’t like it?

15.
but they are slow L

16.
From 1.8.0 ‘manual’ stage!

17.
We still have
to remember
to pre-
commit
install
but*

18.
Run pre-commit on pipeline
or use pre-commit.ci

19.
Can we
remove some
Makefile
commands
maybe?

20.
one ring tool to rule them all

21.
What on Earth is a pyproject.toml?
It’s the specified file format of PEP 518 which
contains the build system requirements of Python
projects.
We can specify configuration data within the [tool]
section!

22.
Poetry
Python packaging and dependency
management made easy the new,
standardized pyproject.toml.
In other words, it replace setup.py,
requirements.txt, setup.cfg,
MANIFEST.in and Pipfile.
Documentation: https://python-
poetry.org/

23.
How the
pyproject.toml
looks like

24.
Poetry 1.2 is coming!
Introduce the ability do
group dependencies in
groups! Not only the
default `dev` one.
And plugins to add your
own functionality to
Poetry!

25.
Thank you!