#pyparsing
Live, measured metrics for the hashtag #pyparsing from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #pyparsing
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-09-26 00:31 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-09-26 00:31 UTCNo related tags with measured usage found for #pyparsing.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-09-26 00:31 UTCEverything below is measured over the latest 37 public posts (spanning ~37156 hours).
Posting hours (UTC) — busiest: 03:00
Languages: English (36) · Russian (1)
Avg boosts / post: 2
Top of the latest posts
If you maintain an open source package, set up a standing search on scholar.google.com for your package name. You'll get gmail notifications of published papers referencing your package. It's truly gratifying to see students and research te
I just released pyparsing 3.2.1 with a very cool addition to the railroad diagrams that pyparsing generates for its parsers - non-terminal diagram elements now link to their definitions elsewhere in the diagram! This is pretty handy when th
Just to report that my 3 open source packages pyparsing, littletable, and logmerger (and by extension, textual, which is used by logmerger) all run successfully on Python 3.13b2 (default build) #python #python313 #pyparsing #littletable #lo
What “pyparsing” means
WikipediaIn computer science, scannerless parsing performs tokenization and parsing in a single step, rather than breaking it up into a pipeline of a lexer followed by a parser, executing concurrently. A language grammar is scannerless if it uses a single formalism to express both the lexical and phrase level structure of the language.
“Scannerless parsing” on Wikipedia (CC BY-SA) →#pyparsing across platforms
every network with a public tag surfaceFollow #pyparsing straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
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/pyparsing