Skip to content

Add Python Developer Tooling Handbook to Resources#3035

Open
tdhopper wants to merge 1 commit intovinta:masterfrom
tdhopper:add-pydevtools
Open

Add Python Developer Tooling Handbook to Resources#3035
tdhopper wants to merge 1 commit intovinta:masterfrom
tdhopper:add-pydevtools

Conversation

@tdhopper
Copy link
Copy Markdown

@tdhopper tdhopper commented Apr 7, 2026

What is pydevtools.com?

pydevtools.com is the Python Developer Tooling Handbook, a comprehensive, freely available guide to modern Python developer tools. It covers:

  • Package management (uv, pip, poetry, pdm, conda)
  • Linting and formatting (Ruff, flake8, black)
  • Type checking (mypy, ty, Pyright)
  • Testing (pytest, tox, nox)
  • Virtual environments, packaging, CI/CD, and more

The handbook follows the Diataxis framework with tutorials, how-to guides, explanations, and reference pages, making it useful for both beginners setting up their first Python project and experienced developers evaluating modern tooling.

Why add it?

The Resources section currently has Newsletters and Podcasts but no Websites subsection. pydevtools.com fills a gap as a curated, maintained resource specifically focused on Python developer tooling — a topic that's seen rapid change with tools like uv and Ruff gaining adoption. It would be valuable to the awesome-python community as a go-to reference for understanding the modern Python toolchain.

Placement

Added under Resources > Websites (new subsection), following the pattern of the existing Newsletters and Podcasts subsections.

@TheAfnan
Copy link
Copy Markdown

Great submission! Here are a few suggestions to strengthen this PR:

  1. Add Evidence of Maintenance & Community.

    GitHub stars, forks, or usage metrics?
    Last update date to confirm it's actively maintained?

    any notable endorsements or citations in the Python community?

  2. Clarify Navigation Structure
    The README doesn't currently show "Resources" as a top-level category in the main table of contents (lines 1-121)
    Confirm if this should be added to the navigation menu at the top for discoverability

3.Strengthen Differentiation

The handbook covers many existing tools already listed (ruff, pytest, poetry)
Clarify what makes this (website resource unique) is it the curated collection, the Diataxis framework approach, or comprehensive coverage?

These are minor suggestionsthe resource itself looks valuable!

@tdhopper
Copy link
Copy Markdown
Author

Great submission! Here are a few suggestions to strengthen this PR:

  1. Add Evidence of Maintenance & Community.

    GitHub stars, forks, or usage metrics?
    Last update date to confirm it's actively maintained?

    any notable endorsements or citations in the Python community?

  2. Clarify Navigation Structure
    The README doesn't currently show "Resources" as a top-level category in the main table of contents (lines 1-121)
    Confirm if this should be added to the navigation menu at the top for discoverability

3.Strengthen Differentiation

The handbook covers many existing tools already listed (ruff, pytest, poetry)
Clarify what makes this (website resource unique) is it the curated collection, the Diataxis framework approach, or comprehensive coverage?

These are minor suggestionsthe resource itself looks valuable!

Thanks for the thoughtful review! To address each point:

Maintenance & community

  • Traffic: ~72k pageviews over the last 90 days

  • Activity: updated daily with over 200 articles

  • Community signal: Charlie Marsh (creator of Ruff and uv, founder of Astral) regularly retweets from the handbook. Agriya Khetarpal, who works on Pyodide and cibuildwheel, recently shared:

    Thank you very much for your handbook, by the way. I do lots of Python packaging at work, and it's been incredibly useful, as a handy reference on Python packaging stuff I am too lazy to write my own notes for!

  • The site also ranks on the first page of Google for many common Python tooling queries.

Navigation placement

Happy to defer to wherever you'd like this to live in the README. A "Resources" section makes sense, but "Documentation" or a standalone entry would work too.

Differentiation from tools already listed

awesome-python lists the tools; pydevtools.com explains which ones to pick, how to use them together, and how to migrate between them. Specifically:

  • Opinionated, not neutral: The handbook takes clear positions (e.g., recommending uv, Ruff, and ty) with honest trade-off analysis
  • Prioritizes beginners: The Python packaging ecosystem is famously disorienting for newcomers; the handbook is written to get someone from zero to a working modern workflow.
  • Up to date: The ecosystem changes fast and regular updates ensure people can find the information they need for tools as they currently are

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants