docs(okf-v0.2): state the PyYAML constraint, not one satisfying version
Upstream requires `pyyaml>=6.0`; 6.0.3 is what the measurement happened to run under. Writing the latter as "the version upstream requires" is the same class of imprecision the surrounding paragraph exists to correct. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012gwLPe5TY5aN3o3tejv9Nh
This commit is contained in:
parent
19b900b4f8
commit
99e5e17c00
1 changed files with 2 additions and 2 deletions
|
|
@ -957,8 +957,8 @@ output is the baseline. Materialize it twice with the *same* explicit
|
|||
and strips a BOM before any caller sees it, so a parsed assertion masks precisely
|
||||
these two defects."
|
||||
|
||||
*Measured against PyYAML 6.0.3 — the version upstream's own `pyproject.toml`
|
||||
requires:*
|
||||
*Measured against PyYAML 6.0.3, which satisfies the `pyyaml>=6.0` that
|
||||
upstream's own `pyproject.toml` requires:*
|
||||
|
||||
| Input | `safe_load` returns | Type |
|
||||
|---|---|---|
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue