-
Notifications
You must be signed in to change notification settings - Fork 0
M10: the funnel and the PEP 545 milestone #16
Copy link
Copy link
Open
Labels
corpus-repoChanges that land in python-docs-vi-machine-translationChanges that land in python-docs-vi-machine-translationdocsREADME, runbook, reportsREADME, runbook, reportsmilestoneA milestone tracking issue, M0 through M10A milestone tracking issue, M0 through M10reviewRound-trip, judge, sampling, the human funnelRound-trip, judge, sampling, the human funnel
Milestone
Description
Metadata
Metadata
Assignees
Labels
corpus-repoChanges that land in python-docs-vi-machine-translationChanges that land in python-docs-vi-machine-translationdocsREADME, runbook, reportsREADME, runbook, reportsmilestoneA milestone tracking issue, M0 through M10A milestone tracking issue, M0 through M10reviewRound-trip, judge, sampling, the human funnelRound-trip, judge, sampling, the human funnel
The funnel and the PEP 545 milestone. Human work, plus deterministic tooling.
Checklist
Last-Translatorupdated per reviewed fileROADMAP.mdrewritten offpydocvi report coverage. The current one says zero words are formally translated, over a repo holding a million words of machine output, and that gap is the thing to fixpydocvi apply --branch 3.14produces the 3.14 catalogs from the same memory, which is what makes the shared-memory claim real rather than assertedExit
bugs.po,tutorial/andlibrary/functions.pofully human-reviewed and submitted through Transifex. The coverage table is generated and true. No claim anywhere in either repository that machine output satisfies PEP 545.