Post #588023

2026-01-28 15:23 UTC

Is there a best practice around setting up a modern Python module repo with pyproject.toml, uv, linting, tox, pytest, coverage, GitHub actions ...? There are so many different approaches, I&#39;m struggling to bring it all together. #Python #GitHub #astral_uv #tox

Replies (3)

@benkiel@typo.social 2026-01-28 15:36

@jenskutilek does feel like there should be!

Open ##1261617
@tortuguita@sfba.social 2026-01-28 15:53

@jenskutilek this guy goes over one example https://m.youtube.com/watch?v=kcfERM6fcgU&pp=ygUZR2x5cGggdGhlIHBlcmZlY3QgcHJvamVjdA%3D%3D

Open ##1261628
@jlarmstrongiv@typo.social 2026-01-28 23:43

@jenskutilek the best is usually what you and your team are familiar with, or whatever is broadly supported in your industry Also, you don’t have to upgrade all at once. It took me a while to switch from asdf to mise and from pip to uv Mise with mise.toml - programming language and tool manager per project (specific versions of Python, Rust, Node.js, etc.) - global packages manager per project (afdko, fontmake, fontspector, etc.) - scripts (called tasks) manager for project-specific bash and python scripts - automatic .venv activation UV - scaffold project and create venv - manage python package dependencies in pyproject.toml - experimental dependency pinning and monorepo support Formatting - ruff Types - basedpyright CI - GitHub Actions Testing - pytest and tox

Open ##1261629