| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Much of bpo-29521 was fixed in parallel with commit e7ffb99 . This cleans up the rest. Apply parallel change to Doc/make.bat to read "set SPHINXOPTS=-D latex_elements.papersize=" I don't have a Windows system on which to observe the warning, but it should be necessary. The warning: .../workspace/cpython_github/Doc/faq/windows.rst:303: WARNING: unknown option: -t In the Windows FAQ, `How do I keep editors from inserting tabs into my Python source?`, contained a reference to a Python -t option. In Python 2.x, this caused Python to issue warnings about lines with mixed spaces and tabs, but as of Python 3.6 it does nothing. Per discussion at http://bugs.python.org/issue29387, take their wording. Python [3] raises an IndentationError or TabError. Tabnanny is now a module. (cherry picked from commit 3d707be)
…p_next(...) Add the required STACKLESS_... macros to taskletobject.c tasklet_kill(...) and wrap_next(). Add a test class. https://bitbucket.org/stackless-dev/stackless/issue/84 (grafted from 5d3898850c2f06d2a57b7589e4b5b8ebd9355e84, af52a8f20449 and 27e7e0fa1709)
This should fix errors like:
File "python3.9/multiprocessing/resource_sharer.py", line 147, in _serve
send, close = self._cache.pop(key)
KeyError: 8
Fixes #84
…DETECTED
Per supervisor [chat L2376] task assignment + testkeeper L2382 execution
+ theologian L2371+L2378 prediction validated. Empirically confirms
void*-typedef drift class IS REAL — W25b promotion required for full
coverage.
EMPIRICAL RESULT (testkeeper executed):
Mutation: hir_c_insert_before 2nd arg HirInstr → struct HirBasicBlock*
in BOTH hir_c_api.h:744 + hir_c_api.cpp:2349 (NO arity change).
Build cmd: scripts/build_phoenix.sh
HEAD: dac46b9 (post-W25 Step C lint gate)
BUILD_EXIT=0 ← DRIFT UNDETECTED at compile time
ZERO compile errors related to hir_c_insert_before. All 6 §1b callers
(licm_c.c x1, pass_output_type_c.c x3, simplify_c.c x2) compiled
silently — caller's HirInstr (= void*) implicitly converted to
struct HirBasicBlock* per C99 §6.3.2.3 with NO diagnostic.
INTERPRETATION per spec §5 + theologian L2371:
BUILD_EXIT=0 (uncaught) → void*-typedef drift REAL → W25b promotion
(HirInstr/HirRegister/HirFunction void* → struct ptr) REQUIRED for
full drift surface coverage.
CUMULATIVE §5.3 PICTURE:
ARITY mutation (push 67 baseline + push 76 PASS): closed by Step B + C
canonical includes. Caught at compile (BUILD_EXIT=2 = good).
TYPE-ONLY mutation on void*-aliased handles (THIS): UNCAUGHT.
C99 implicit void*↔struct-ptr conversion masks the drift.
W25 OUTCOME:
ARITY drift on canonical-included paths: CLOSED (Step B + C, push 75 + 77b)
TYPE-ONLY drift on void*-aliased handles: OPEN — W25b required
CHANGES: appended POST-STEP-B-FINAL section to
docs/w25-step-b-mutation-baseline.txt (PRE-STEP-B in push 67
911e173; POST-STEP-B arity in push 76 74bf7fc; POST-STEP-B-FINAL
type-only HERE).
Per pythia python#84 framing precision + supervisor L2376: 'arity-drift
surface closed; void*-typedef drift OPEN per push 78 type-only result'.
W25b decision now front-of-queue before INVOKE_* Phase 2.
testkeeper STRICT verify N/A for docs-only commit. Light-scrutiny
gatekeeper APPROVE expected.
AUTHORSHIP: testkeeper executed §5.3 type-only procedure (chat L2382);
generalist commits artifact per role boundary (push 67 + 76 precedent).
Authorization chain:
- W25 spec §5 + §7 caveat: theologian L2017 + L2329 (3) + L2334
- TYPE-ONLY mutation choice + endorsement: testkeeper L2380 + theologian L2378
- Push 78 sequencing: supervisor L2376
| Back | FazBrowse Home | New Git URL |
Much of bpo-29521 was fixed in parallel with commit
e7ffb99 . This cleans up the rest.
Apply parallel change to Doc/make.bat to read
"set SPHINXOPTS=-D latex_elements.papersize="
I don't have a Windows system on which to observe the warning,
but it should be necessary.
The warning:
.../workspace/cpython_github/Doc/faq/windows.rst:303:
WARNING: unknown option: -t
In the Windows FAQ, How do I keep editors from inserting tabs into my Python source?, contained a reference to a Python -t
option. In Python 2.x, this caused Python to issue warnings
about lines with mixed spaces and tabs, but as of Python 3.6
it does nothing.
Per discussion at http://bugs.python.org/issue29387, take
their wording. Python [3] raises an IndentationError or
TabError. Tabnanny is now a module.
Contributed by Jim DeLaHunt @JDLH
(cherry picked from commit 3d707be)