Update README file extensions to .rst by taycaldwell · Pull Request #105 · python/cpython

taycaldwell · 2017-02-15T02:03:25Z

Updated the file extensions of the README files in the repo to have the .rst file extension so they are rendered properly on GitHub.

ghost · 2017-02-15T02:25:03Z

Not all of them should be a simple rename, see if you can bring .rst formatting in the mix.

refi64 · 2017-02-15T03:22:27Z

If you want, you can also use some of the stuff I did in #5

taycaldwell · 2017-02-15T04:50:26Z

@rogersachan Files have now been fixed and updated with proper .rst formatting with respect to how GitHub renders them. A lot of the existing files used proper syntax and looked fine. For those files I just added the file extension so they could be rendered properly.

The biggest formatting changes were applied to the PCBuild README.

codecov · 2017-02-15T05:14:42Z

Codecov Report

❗ No coverage uploaded for pull request base (master@984eef7). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #105   +/-   ##
=========================================
  Coverage          ?   82.38%           
=========================================
  Files             ?     1428           
  Lines             ?   351164           
  Branches          ?        0           
=========================================
  Hits              ?   289315           
  Misses            ?    61849           
  Partials          ?        0

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 984eef7...e3e0d5f. Read the comment docs.

brettcannon · 2017-02-15T19:18:00Z

Would it be possible to break this PR up into separate ones per file? I know that might be a pain but it would make it easier to review since e.g. I don't know if @zooba and @zware actually want to the READMEs related to Windows builds to change (plus you stripped out Windows line endings in those files).

brettcannon · 2017-02-15T19:18:58Z

GH-104 renames Doc/README.rst as well.

taycaldwell · 2017-02-15T22:25:51Z

@brettcannon I'm fine with breaking it down into multiple PRs.

zooba · 2017-02-15T23:26:13Z

I'm not concerned about this one (though the other readme "fix" broke our release builds...). Ideally we'd have a .txt version there too so that it's easy to read the file from a clone/tarball, but if the GitHub masses would prefer .rst then I'd rather only have one copy. It's hard enough to keep it up to date already...

brettcannon · 2017-02-15T23:28:10Z

OK, then let's do this file-by-file as there's so many PRs flying by that are grabbing this sort of low-hanging fruit it's probably best to do this slowly and methodically so that @taycaldwell doesn't have to constantly rebase because someone did another README.

…e in slp_kill_tasks_with_stacks Fix the bug and add a test case. https://bitbucket.org/stackless-dev/stackless/issues/105 (grafted from f7deec75f44dba55bea628b62f89f3c1706bdb68)

Closes #105 (I'm a bot 🤖)

…DE.md Bundle of two theologian-authored doc amendments per supervisor dispositions: CLAUDE.md (+2L) — Pre-Edit WT Integrity 'undiagnosed-recurring' honest framing per pythia python#105 (3) + supervisor 02:13:12Z + theologian 02:13:54Z. Acknowledges 5+ prior incidents closed at SYMPTOM layer without root-cause attribution; this 4-step discipline codifies reactive HALT, not automated detection. Detection still depends on agent noticing mid-edit. Recurrence-prevention claim does not exceed what text mechanizes; automated detection feasibility (file-watcher / git-hook) is fixup PIR territory and remains open. docs/tier8-class-b-cport-migrate-arm-spec.md (+93/-20) — pythia python#104 amendments per theologian 01:38:08Z + supervisor 01:38:26Z + 01:37:05Z: §1.1 container-shape transferability caveat (vector-pilot ≠ hash/ stack/allocator-shape pattern transferability) §5 python#11 NEW: bridge-count-delta acceptance (each pilot must NET- SUBTRACT bridges OR honestly add with W45 fixture coverage) §5 python#12 NEW: Phase B FORCING-FUNCTION (Tier 8 SECOND-PILOT block_map_ Step A BLOCKED until exception_table_ Phase B commit lands) Bundle scope: doc-only, no §3.5 BUILD MODE (no builder*.{cpp,h,c} touched). Atomic per supervisor 02:13:12Z + 01:38:26Z dispositions. Push 28 advances the Tier 8 Phase A resume deadline tracker per theologian 02:13:54Z + supervisor 02:13:12Z (push 28 OR session-end whichever first). If Alex disposition + fixup PIR not received by deadline, theologian amends Phase 3 closure summary fa8dfef to remove Tier 8 pilot citation + re-opens pythia python#103 escape question.

…xtension Per supervisor 02:35:05Z (PIR redirect to theologian) + 02:37:20Z (GO atomic commit + Tier 8 Phase A resume directive). Theologian 02:36:49Z PIR delivery + 4-section CLAUDE.md amendment. PIR scope (docs/2026-04-24-pre-edit-revert-pir.md, 132L NEW): (1) Automated-detection feasibility — 3 options analyzed: (a) inotify file-watcher daemon: feasible but multi-session NBS-suite extension; DEFERRED to W48 (b) pre-commit git hook: REJECTED (duplicates gate python#3) (c) agent-side mtime-checkpoint discipline: ADOPTED (~5L per agent edit-loop; in-session feasible) (2) Per-incident root-cause attribution for 5 priors + this incident: D-1775810621 / D-1775669703 / D-1776414469 — SYMPTOM-only D-1776434533 — DIRECTIVE-only (Alex 'always full commit checkouts') D-1776887480/D-1776890644 — GATE-hardening (gate python#3 added) 2026-04-24T01:23Z — SYMPTOM-only (observed-but-not-attributed) TOTAL: 6 incidents, 0 root-cause attributions (3) Class CONFIRMED 'undiagnosed-recurring' (already labeled in CLAUDE.md amendment e8a83df per pythia python#105) CLAUDE.md mtime-checkpoint extension (+1L net, rule 1 enhancement): Pre-edit baseline now also captures per-touched-file mtime via `stat -c %Y %n`; verify before each subsequent write within edit sequence. mtime mismatch = external revert; HALT. Mechanizes detection vs requiring agent to notice mid-edit. Bundle scope: doc-only (PIR file + CLAUDE.md edit), no §3.5 BUILD MODE per touched-files rule. Atomic per supervisor 02:37:20Z. Phase 3 closure-amendment (docs/tier7-phase3-closure-summary.md) remains STAGED on disk per theologian 02:36:49Z + supervisor 02:37:20Z ('RETRACT only on successful Phase A resume push'). NOT committed this commit. Tier 8 Phase A resume armed post-push 29 per supervisor 02:37:20Z GO (R-retry) — PIR + mtime-checkpoint discipline mechanizes recurrence detection; don't infinitely block on Alex when discipline armed.

…hon#7) Per supervisor 02:45:37Z fast-path TRIGGER post Tier 8 Phase A incident python#7 (R-retry under enhanced mtime-checkpoint discipline also ROLLED BACK at HEAD 48339e2, same pattern as 01:23Z incident python#6). mtime-checkpoint discipline DETECTED proactive (Write tool safety check + post-write system-reminders) but did NOT prevent recurrence. (R-retry) reasoning ('discipline addresses risk class') empirically INVALIDATED — same external force re-reverts at every Tier 8 attempt. Pythia python#105 'fever has name infection still spreads' validated twice. Theologian-pre-drafted amendment 02:26:02Z replaces 'Tier 8 pilot scheduled' section with 'Tier 8 pilot BLOCKED (push 28+, 2026-04-24)': - Pilot field exception_table_ POD-equivalent - Phase A attempted 01:18:35Z + 02:39:00Z (R-retry); HALTED 01:23:55Z + 02:45:12Z by external file-state revert (incidents python#6 + python#7; observed-but-not-attributed per generalist 01:24:43Z + 02:45:12Z) - Resume gated on Alex disposition + fixup PIR; both unmet by push 28 deadline (supervisor 02:13:12Z + theologian 02:13:54Z) - DEADLINE reached push 28 at 02:15:47Z; second incident at 02:45:12Z re-confirms permanent-block-this-session **Pythia python#103 escape question RE-OPENED.** Phase 3 keep-bias is the END STATE pending future migrate-arm validation. 'Transitional foundation cost paid back' framing is HONEST-ASPIRATIONAL not RESOLVED. ZERO-C++ terminal goal (MEMORY.md L70 + L104) remains gated on Tier 8 pilot landing in a future session. Phase 3 cumulative +257L is END STATE this session. Future session must re-attempt Tier 8 Phase A under same spec (post external-revert root-cause attribution, since detection alone insufficient) OR honestly amend Phase 3 closure framing to 'permanent scaffolding'. Cross-link section also amended: §5 amendment line updated to 'keep-bias as design choice; Tier 8 migrate-arm pilot FILED but BLOCKED — see Tier 8 pilot BLOCKED section above'. Doc-only +24L. No §3.5 BUILD MODE per touched-files rule. Authorization: theologian 02:26:02Z STAGED-ON-DISK + supervisor 02:45:37Z fast-path TRIGGER post HALT python#7.

…amendment Per supervisor 02:48:39Z atomic doc-only bundle. Closes the 6→7 escalation triggered by Tier 8 pilot Phase A (R-retry) recurring revert at incident python#7. W48 spec (docs/w48-nbs-inotify-file-watcher-spec.md, +194L NEW): Theologian 02:48:25Z spec per W42/W44/W45 spec pattern. Elevates PIR §2.1 option (a) inotify file-watcher from DEFERRED to ACTIVE workstream. Mechanism: pyinotify daemon as NBS-suite sidecar; narrow watch per agent edit-set; event correlation with agent Write tool calls; forensic snapshot for root-cause attribution (closes pythia python#105 (3) zero-attribution gap). 4-escalation history honest framing: Alex directive D-1776434533 → gate python#3 D-1776887480 → 4-step discipline 03a0dcb → mtime-checkpoint 48339e2 → W48. Each progressively detective, none preventive. Cost ~3-5 sessions multi-session NBS-suite extension. Acceptance: 7 items including CLAUDE.md rule 5 addition + Tier 8 pilot retry under W48. PIR amendment (docs/2026-04-24-pre-edit-revert-pir.md, +21/-2): - Incident table: appended incident python#7 (2026-04-24T02:45Z, same pattern as python#6, mtime-checkpoint detected but did not prevent) - Conclusion: 7 incidents (was 6), 0 root cause attributions - NEW 'Incident python#7 ESCALATION' subsection: documents (R-retry) reasoning empirically INVALIDATED + pythia python#105 'fever has name' validated twice - NEW 'W48 ESCALATION' subsection: cross-links W48 spec landing + Tier 8 pilot Phase A retry GATED on W48 landing Doc-only bundle, no §3.5 BUILD MODE per touched-files rule. Closes the post-incident-python#7 reactive cycle: closure-amendment shipped at push 30 (f6328cd), W48 + PIR ship at push 31. Authorization: theologian 02:48:25Z (W48 spec) + supervisor 02:48:39Z (atomic bundle GO).

ROOT CAUSE FIX for the 8-incident undiagnosed-recurring file-state revert class (D-1776998268 + 7 priors). Per supervisor 04:14:27Z post-incident-python#8 ROOT CAUSE IDENTIFICATION: the §3.5 falsifier's restore_files() trap was the "external reverter" across all 8 incidents. It ran `git checkout HEAD --` on TOUCHED_FILES on script exit; if those files had unstaged modifications BEFORE the script ran (e.g., agent's in-flight Tier 8 Phase A content), the trap blew them away. Empirical validation (this session 04:13:36Z): - Test python#6 + python#7 (trivial content, single-mechanism): no revert - Tests python#5/python#7 idle: no revert - cmake build alone: no revert - §3.5 invocation on staged Phase A: REVERT (PhxExceptionTable count 13 → 0; mtime bumped 1777002918 → 1777003987; builder_state_c.h no longer M in git status) 8 prior incidents now retroactively attributed to §3.5 trap firing during build/gate cycles concurrent with agent Tier 8 attempts. NO external actor (no VS Code, no Alex, no formatter, no cron). W48 inotify daemon NOT NEEDED. (Iso-A) host relocation NOT NEEDED. Class size CLOSED — class type changed from "undiagnosed-recurring" to "self-inflicted via §3.5 trap, RESOLVED". Fix mechanism: snapshot per-file content to /tmp on first snapshot_file_if_new() call (per fixture mutation start). restore_files() copies from snapshot (not HEAD), preserving pre-script unstaged state. Snapshots cleaned + FILE_SNAPSHOTS array unset post-restore. Re-validation (this session post-fix): - §3.5 BUILD MODE 4/4 PASS - post-restore build [OK] - Phase A content (PhxExceptionTable count 13) SURVIVED §3.5 invocation - ALL 6 Tier 8 staged files still M Doc-only (script-only) push, no §3.5 BUILD MODE per touched-files rule (this IS the §3.5 script being amended; meta-circular but doc-only gate appropriate). Authorization: supervisor 04:14:27Z FIX directive post-ROOT-CAUSE identification (generalist 04:13:58Z catch). Pythia python#105 'fever has name infection still spreads' was structurally correct re self-inflicted infrastructure — but the infection wasn't external-class undiagnosable; it was OUR OWN script's exit trap trampling unstaged work. 5 detection layers (Alex directive D-1776434533, gate python#3 D-1776887480, 4-step Pre-Edit WT Integrity D-1776995670, mtime-checkpoint D-1776998268, W48 spec D-1776999077) added to detect ourselves. Audit own scripts BEFORE external-actor hypotheses (per new feedback memory entry).

Per docs/tier8-class-b-cport-migrate-arm-spec.md theologian 01:01:50Z + supervisor 01:02:46Z ADOPTED + supervisor 01:18:35Z + 03:44:19Z + 04:14:27Z (8-incident root-cause attribution to §3.5 restore-trap + b83f084 fix LIVE). Migrates HIRBuilder std::vector<ExceptionTableEntry> exception_table_ field to PhxExceptionTable (purpose-built typed-inline pure-C container in PhxHirBuilderState.exception_table_phx). Validates Pythia python#103 + python#94 (3) §5 forcing-decision MIGRATE-ARM via 1-pilot port (vs Phase 3's 4-Class-B-kept disposition). CONTAINER: PhxExceptionTable (builder_state_c.h): typed-inline data/count/capacity with 6 inline funcs (init/destroy/push/size/at/clear). Lazy-init, doubling realloc, free at HIRBuilder dtor. ExceptionTableEntry (builder_state_c.h): POD mirror of deleted C++ struct, fields flattened BCOffset → int + bool → unsigned char. C BODY PORTS (builder_state_c.c): hir_builder_state_init: also calls phx_exception_table_init hir_builder_state_destroy: NEW (calls phx_exception_table_destroy) parse_exception_table_c: pushes ExceptionTableEntry via phx_exception_table_push (replaces deleted push_cpp bridge) find_exception_handler_c: linear scan via phx_exception_table_size + at (replaces deleted size_cpp/entry_cpp bridges) C++ SHIM (transient compatibility per Phase A; Phase B deletes): HIRBuilder::parseExceptionTable → 1-line delegate to C body HIRBuilder::findExceptionHandler → C body returns index, shim converts via phx_exception_table_at preserving caller-contract HIRBuilder::buildHIRImpl translate-loop iterates PhxExceptionTable via size+at; .clear() goes to phx_exception_table_clear HIRBuilder::getSimpleExceptInfo wraps handler.target in BCOffset{} (now plain int post-C struct migration) emit_call_method_exception_handler_inline_c at builder.cpp:2883 still calls self->findExceptionHandler (KEPT shim — Phase B will rewire) DELETED: 3 _cpp bridge impls in builder.cpp (push/size/entry, ~37L) 3 friend decls in builder.h C++ struct ExceptionTableEntry in builder.h (5L) std::vector<ExceptionTableEntry> exception_table_ field in builder.h W45 §1-§2 fixture removals (3): the deleted bridges no longer have signatures to fuzz. Cumulative bridge-count delta: -3 (per Tier 8 spec §5 python#11 acceptance). Numstat (vs HEAD b83f084): Python/jit/hir/builder.cpp +21 -44 (-23 NET) Python/jit/hir/builder.h +14 -19 (-5 NET) Python/jit/hir/builder_state_c.c +30 -17 (+13 NET) Python/jit/hir/builder_state_c.h +103 -48 (+55 NET) scripts/w45_bridge_drift_falsifier.sh +0 -3 (-3 NET) TOTAL: NET +37L, bridge-count delta -3. Per Tier 8 spec §5 python#10 amendment (theologian 01:14:29Z): full Tier 8 endpoint ≤+0L cumulative is across all 4 Class B containers, not single pilot. exception_table_ pilot subtracts ~19% of Phase 3 +257L foundation cost; Phase 3 + Tier 8 Phase A cumulative now +257 + 37 = +294L. Apply mechanism: python single-process write (8-incident root cause was §3.5 restore-trap, NOT Write-tool-burst — but python single-process remains best practice per Pythia python#107 (4) isolation principle). Apply script: /tmp/apply_phase_a.py. EXPANDED PRE-COMMIT GATE per supervisor 01:17:23Z (testkeeper 04:24:49Z): Stage 1 compile-check: BUILD_EXIT=0 Stage 2 §3.5 BUILD MODE: 4/4 PASS, PhxExceptionTable INTACT post (§3.5 fix b83f084 VINDICATED) Stage 3 per-bench gate: GEO 1.27x, all 4 floor criteria PASS §5 forcing-decision MIGRATE-ARM EMPIRICALLY VALIDATED via this pilot: exception_table_ migrated to PhxArray-equivalent pure-C container without C++-side-keep dependency in C-side reads. Pattern propagatable to remaining 3 Class B containers (block_map_, temps_, static_method_stack_) in future Tier 8 batches per spec §1.1 container-shape transferability caveat. Phase B follow-up commit (NEXT) deletes C++ shims + rewires the remaining caller at builder.cpp:2883 per Tier 8 spec §5 python#5. Authorization: supervisor 03:44:19Z + 04:14:27Z; theologian 03:33:50Z patch-apply hybrid + 03:54:15Z content-trigger refinement (later attributed to §3.5 trap, not content) + 04:14:27Z fix directive. Cross-link: 8 incidents resolved via b83f084 §3.5 restore-trap fix. Pythia python#105 'fever has name infection still spreads' RESOLVED — fever was self-inflicted instrumentation. W48 spec marked CANCELLED post- this-commit per supervisor 04:14:27Z cascade re-retract.

Per pythia python#111 (4) + supervisor 05:59:04Z + theologian 05:59:52Z. Reform addresses ritualization risk identified in pythia python#111: 2 retro- frames already happened (meta-rule self-violation D-1777005990 + push-36 race-window citation rule); a third would calcify 'gate becomes ritual that activates only when pythia surfaces the omission.' Reform: cost-benefit + 8-incident-cite required AT AUTHORING of new procedural rules, NOT retroactively. Retro-frames acknowledge violation but do not satisfy the meta-rule. Authors who skip framing must self- flag and provide framing in follow-up BEFORE rule treated as adopted. Cost-benefit (per the meta-rule it codifies): - Cost: ~0 procedural — discipline change only - Benefit: blocks ritualization failure mode pythia python#111 (4) named - 8-incident-cite: pythia python#105 'fever has name infection still spreads' framing — adding rules without addressing root cause repeats pattern; reform addresses root cause (ritualization) not surface (rule count) Doc-only +2L (paragraph wrap; logical 6L per theologian count). Authorization: theologian 05:59:52Z + supervisor 05:59:04Z (4) ADOPTED. Atomic doc commit, expedited APPROVE per supervisor directive.

taycaldwell added 11 commits February 14, 2017 20:45

Rename README.txt to README.rst

8071acb

Rename README to README.rst

d9c2563

Rename README to README.rst

14be2f1

Rename README to README.rst

ec51512

Rename README to README.rst

13b7241

Rename readme.txt to readme.rst

3356de7

Rename readme.txt to readme.rst

d86a6d5

Rename README to README.rst

56150b5

Rename README to README.rst

8c2ad0d

Rename README to README.rst

14d769e

Update README.rst

c0d7ad0

the-knights-who-say-ni added the CLA signed label Feb 15, 2017

taycaldwell added 2 commits February 14, 2017 22:09

Update file table so it renders properly.

3af48ee

Update .rst formatting

615facf

taycaldwell added 2 commits February 14, 2017 23:21

Update README with .rst formatting

9122fa2

Update README with proper .rst formatting.

e3e0d5f

brettcannon closed this Feb 15, 2017

akruis pushed a commit to akruis/cpython that referenced this pull request Sep 9, 2017

merge 3.3-slp (Stackless python#105)

b0789ae

akruis pushed a commit to akruis/cpython that referenced this pull request Sep 9, 2017

merge 3.4-slp (Stackless python#105)

6d81d99

ghost mentioned this pull request Sep 24, 2017

Assertion violation introduced by #81 stackless-dev/stackless#103

Closed

jaraco pushed a commit that referenced this pull request Dec 2, 2022

🤖 Format code using black (#106)

9ee5393

Closes #105 (I'm a bot 🤖)

gvanrossum mentioned this pull request Aug 22, 2023

heap-use-after-free in _PyFunction_LookupByVersion #108253

Closed

ngoldbaum mentioned this pull request Sep 23, 2024

Crash running PyO3 tests with --test-threads=1000 #124375

Closed

This was referenced Feb 11, 2025

segmentfault when pip installing setuptools #129992

Open

segmentfault when pip installing setuptools #129993

Closed

sergey-miryanov mentioned this pull request Dec 18, 2025

Observed memory leak in ssl library: Python 3.14 GC issue #142516

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Update README file extensions to .rst#105

Update README file extensions to .rst#105
taycaldwell wants to merge 15 commits intopython:masterfrom
taycaldwell:master

taycaldwell commented Feb 15, 2017

Uh oh!

ghost commented Feb 15, 2017

Uh oh!

refi64 commented Feb 15, 2017

Uh oh!

taycaldwell commented Feb 15, 2017 •

edited

Loading

Uh oh!

codecov Bot commented Feb 15, 2017

Uh oh!

brettcannon commented Feb 15, 2017

Uh oh!

brettcannon commented Feb 15, 2017

Uh oh!

taycaldwell commented Feb 15, 2017

Uh oh!

zooba commented Feb 15, 2017

Uh oh!

brettcannon commented Feb 15, 2017

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

Uh oh!

Conversation

taycaldwell commented Feb 15, 2017

Uh oh!

ghost commented Feb 15, 2017

Uh oh!

refi64 commented Feb 15, 2017

Uh oh!

taycaldwell commented Feb 15, 2017 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

codecov Bot commented Feb 15, 2017

Codecov Report

Uh oh!

brettcannon commented Feb 15, 2017

Uh oh!

brettcannon commented Feb 15, 2017

Uh oh!

taycaldwell commented Feb 15, 2017

Uh oh!

zooba commented Feb 15, 2017

Uh oh!

brettcannon commented Feb 15, 2017

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

taycaldwell commented Feb 15, 2017 •

edited

Loading