#pydoc
Live, measured metrics for the hashtag #pydoc from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #pydoc
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-27 13:45 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · fosstodon.org (Mastodon public search API) · fetched 2026-07-27 13:45 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 13:45 UTCEverything below is measured over the latest 6 public posts (spanning ~21165 hours).
Posting hours (UTC)
Languages: English (5) · German (1)
Avg boosts / post: 0.7
Top of the latest posts
#python stdlib has a generated code documenter shoved into it: #pydoc. It has a lot of design problems, top of which is that it works poorly as a pure CI task to generate static HTML. I forked it and made it at least usable, albeit still ug
Maybe not, pydoc-markdown (https://github.com/NiklasRosenstein/pydoc-markdown) looks like it just yanks out the right parts, and doesn't do any filtering or manipulating. Score! #python #markdown #pydoc-markdown
OK, #python question: How do I generate docs for an embedded python project that uses a #SWIG generated library? #pydoc #pdoc and the like rightly complain about non-existent modules, but all the information I want is contained in docstring
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/pydoc