Programming standards
Python — the ProfessNet standard
Style, typing, project structure, FastAPI, tests and code quality.
- 0110 minStyle: PEP 8, black, ruff (formatting and linting)intro
How to keep Python code in ZEUS uniform, automatically formatted and free of lint issues.
- 0211 minStatic typing and mypycore
Type annotations and mypy as a safety net for the ZEUS backend.
- 0310 minProject structure, venv and dependenciescore
How we organize modules, isolate the environment and pin dependencies in ZEUS services.
- 0413 minFastAPI in practice (routers, Pydantic, dependencies)core
Routers, Pydantic models and dependency injection — the patterns we use in the ZEUS API.
- 0512 minAsynchrony: async/await, asyncioadvanced
How to write correct async code in ZEUS and not block the event loop.
- 0612 minTesting with pytest (fixtures, mocks)core
How we write tests in ZEUS: pytest, fixtures, mocks and async tests.
- 0712 minSecurity and quality (bandit, secrets, error handling)advanced
bandit scanning, secret management and correct error handling in ZEUS code.
Check your knowledge — quiz
5 questions · pass mark 80%. Score saved locally.
1.Which tools do we use to format and lint Python?
2.Why do we use static typing and mypy?
3.Which web framework does the ZEUS backend use?
4.How do we isolate a Python project's dependencies?
5.What is bandit for?