#PyYAML
Live, measured metrics for the hashtag #PyYAML from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #pyyaml
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:41 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:41 UTCNo related tags with measured usage found for #pyyaml.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 13:41 UTCEverything below is measured over the latest 17 public posts (spanning ~48052 hours).
Posting hours (UTC) — busiest: 05:00
Languages: English (12) · Polish (4) · German (1)
Avg boosts / post: 1.1
Top of the latest posts
The #PyYAML problem is only getting better. People are trying really hard to make their things work again. Apparently there's a way to force constraints on pip but it's not a perfect solution either. I have two thoughts about this: 1. *Fina
Fun fact: #Azure Pipelines don't support #YAML files with anchors/aliases. Also fun fact: both #PyYAML and #RuamelYAML *insist* on emitting anchors/aliases, and at least the PyYAML authors seem pretty, errr, opinionated on emitting them. ht
@mgorny Did I see correctly that maintainer claims 5.4 release "long gone" and at the same time gates the fix on *Windows Python 2.x*? #pyyaml #cython #python
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/pyyaml