CodeSampleX

Recordspypipycparser2.22

Which symbol ran where

Symbols × operating systems for this version. Cells drill into the package's compatibility cube.

3 52026-08-18
alpine musl11
pycparser.c_ast 100%1
pycparser.c_parser 50%2
pycparser.c_parser.CParser 100%1
pycparser.c_parser.CParser.parse
pycparser.c_parser.ParseError 100%1
pycparser.plyparser.ParseError 50%2

Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.

A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.

Environment detail

Project-level observations and symbol/contract verifications are counted separately and never combined.

These counts do not distinguish how the symbol was called: overloads, argument shapes and options are pooled together. What a particular call shape does is proven by a sample's contract, not by these numbers.

Environment Confidence Observations Verified Pass rate Peers Last seen
python 3.10 · Python · pip · windows
Observations: PROJECT_PROCESS 2✓ 1✕
LOW 3 0 67% 1 2026-08-18
python 3.12 · Python · pip · linux musl · docker
Observations: PROJECT_LOAD 2✓ · PROJECT_TEST 2✓ — Usage: USED 2✓ — Verified: CONTRACT 4✓
MEDIUM 4 +2 4 100% 1 · 2✓ 2026-08-30

Recent failure clusters

Symbols