Automate cleaning code in few easy steps!
How annoying is it to find out that everything went to hell on the pipeline because you forgot to run the formatters? Don’t waste precious time and learn how it is possible to automate these little things, but most importantly understand why it is important to have them in your code! Have you ever been in a situation where you check your pipelines to see if he’s finished running the tests and you find that he hasn’t even started because you forgot to run the linters locally? I contribute to the development of PyCon Italia, Strawberry GraphQL and Poetry Package Manager and coding with these organizations I discovered fantastic tools such as pre-commit, Poetry and many others. In this talk I would like to share with you my findings, think about the pros and cons and understand a little bit better why you should start using them. The Author: Ester Beltrami I'm a Python Developer living in London who is passionate about clean code and architecture. I try to give my contribution to the development of PyCon Italia, Strawberry GraphQL and Poetry Package Manager.
Recommended
Recommended
More Related Content
Similar to Automate cleaning code in few easy steps!
Similar to Automate cleaning code in few easy steps! (20)
Recently uploaded
Recently uploaded (20)
Automate cleaning code in few easy steps!
- 1. Automate cleaning code in few easy steps! Ester Beltrami Twitter: @esterbeltrami GitHub: github.com/estyxx
- 3. CLEARANCE JUST GOT BETTER New lines added Up to 50% off
- 4. We write some code
- 5. We push the code
- 6. Time to relax and wait
- 7. We came back to the pipeline and…
- 8. pre-commit
- 10. 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
- 11. Django hooks! • pre-commit-hooks-django to not forget to commit the migrations files!! • django-upgrade to upgrade Django syntax
- 12. not only code quality, also security!
- 13. What are the benefits?
- 14. Identify issues *before* the code review
- 16. Why developers don’t like it?
- 17. but they are slow L
- 18. From 1.8.0 ‘manual’ stage!
- 19. We still have to remember to pre- commit install but*
- 21. Run pre-commit on pipeline or use pre-commit.ci
- 23. one ring tool to rule them all
- 24. 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!
- 25. 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/
- 27. 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!
- 30. sync Poetry & pre- commit, how to? Our last hook: sync_with_poetry
- 31. Thank you! Twitter: @esterbeltrami GitHub: github.com/estyxx