3.6 by Dark417 · Pull Request #354 · python/cpython
and others added 30 commits
(cherry picked from commit 79ab8be)
It took me quite a bit to figure out what this was referring to, since the given issue number is wrong, and the original commit message I found through git blame lists a different, also wrong issue number... see https://bugs.python.org/issue27122#msg279449 (cherry picked from commit af88e7e)
various updates from upstream python/typing repo: - Added typing.Counter and typing.ChainMap generics - More flexible typing.NamedTuple - Improved generic ABC caching - More tests - Bugfixes - Other updates * Add Misc/NEWS entry (cherry picked from commit b692dc8)
* Fix some deprecation warnings in Doc/conf.py * Fix an rst error in Misc/NEWS Contributed by Ryan Gonzalez @kirbyfan64 (cherry picked from commit e7ffb99)
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)
(cherry picked from commit 7e147f1)
(cherry picked from commit 6420088)
* Travis CI: run rstlint.py in the docs job (#68) Currently, http://buildbot.python.org/all/buildslaves/ware-docs buildbot is only run as post-commit. For example, bpo-29521 (PR#41) introduced two warnings, unnotified by the Travis CI docs job. Modify the docs job to run toosl/rstlint.py. Fix also the two minor warnings which causes the buildbot slave to fail. (cherry picked from commit 2b50186) * Doc/Makefile: set PYTHON to python3 (#124) rstlint.py run by "make check" doesn't support Python 2. "make venv" runs "$(PYTHON) -m venv", whereas Python 2 doens't provide the venv module: it's a module of Python 3 standard library. (cherry picked from commit 91b0e7d)
``local.getlocale(locale.LC_CTYPE)`` and ``locale.getpreferredencoding(False)`` may give different answers in some cases (such as the ``en_IN`` locale). ``re.LOCALE`` uses the latter, so update the test case to match.
* Add .travis.yml to 3.6 branch * Travis CI: run rstlint.py in the docs job (#68) Currently, http://buildbot.python.org/all/buildslaves/ware-docs buildbot is only run as post-commit. For example, bpo-29521 (PR#41) introduced two warnings, unnotified by the Travis CI docs job. Modify the docs job to run toosl/rstlint.py. Fix also the two minor warnings which causes the buildbot slave to fail. * Only run CI checks when appropriate files have changed (#74) Closes python/core-workflow#14 * Use 'make check' instead of 'python3 tools/rstlint.py' (#96)
* Drop duplicate word 'object' in lzma docs * Fix typo in os docs: fpr -> for (cherry picked from commit d4d4874)
(cherry picked from commit b2ee40e)
) * Fix incorrect handling of signed zeros for complex-related classes. * Add Misc/NEWS entry. (cherry picked from commit 112ec38)
(cherry picked from commit fb8fe72)
…no longer affects a partial object after creation. (#209)
(cherry picked from commit 3a9ac82)
Clarify that methods take a string which is interpreted as a regex, not a regex object. Also clarify what the old `-1`, `0`, `1` and `2` options were. (cherry picked from commit 8fb1f6e)
(cherry picked from commit 132ac38)
mention bpo-28929 in the Documentation section of What's New in Python 3.6.1 release candidate 1
(cherry picked from commit dea1536)
) (cherry picked from commit 46ce759)
) Patch by Aviv Palivoda. (cherry picked from commit fe70d92)
(cherry picked from commit 6b4a5f4)
(cherry picked from commit 1f5639c)
…matting operations (#95)
Patch by Matthias Bussonnier. (cherry picked from commit 160edb4)
jaraco pushed a commit that referenced this pull request
Co-authored-by: Terry Jan Reedy <tjreedy@udel.edu> Co-authored-by: Mariatta <Mariatta@users.noreply.github.com>
SonicField added a commit to SonicField/cpython that referenced this pull request
Per supervisor 13:07:53Z disposition of pythia python#354(3): v0.1 specified diagnostic signals (high-WHC -> working-memory failure, etc.) but no concrete intervention, leaving the methodology with an undefined response lever after v2.x moratorium closes the rule-iteration path. v0.2 adds §"Per-class behavioral interventions" specifying operational practices per outcome class: - High-WHC: compose-time A10/A10.1 self-check, 60s cooling-off, mid-compose checkpoint for >=1min compose, restart-cycle reminder - High-MF: gap-class logging, 3+ events triggers scope-review, default to REPORTED/DISPUTED framing for out-of-scope claims - Low-TP: 14-day load-bearing review, distinguish dormant from chilling effect via TN-citation count - TN: encourage citation, no requirement - Cross-class: disposition-side [A10-CLASS: TP|WHC|MF|TN] tagging convention to convert data collection from retro-mining to chat-search ALL practices are existing-rule reapplication or institutional discipline, NOT new rule additions. v2.x moratorium D-1778554524 remains in force. Anti-pattern guard added: intervention catalog must NOT itself become rule corpus; v3 corpus rebuild may legitimately codify some practices, this sections role is to prevent premature codification during v2.x. Self-falsifying disclaimer extended (items 5-7) per feedback_arch_completeness_disclaimer. DO NOT PUSH yet (per supervisor 12:58:10Z directive, push held until c2 lands; ABBA + post-ARM64 APPROVE chain still in flight).
SonicField added a commit to SonicField/cpython that referenced this pull request
Authored 2026-05-12 per supervisor 12:55:33Z dispatch (pythia python#353 extended-block-contingency commitment), during the ~17.5hr c2 ASGuard data_staging block. Read-only investigation + documented procedure for the case where devgpu004 substrate (HEAD/c2 patch series/saved binary) becomes unavailable before c2 push completes. Sections: (a) alternative ARM64 host availability — none documented; alt-host spawn requires Alex coordination (b) bundle file size + transport mechanism — 4-patch series 65 KB, git bundle 67 KB, full-repo bundle 524 MB; direct scp verified (c) saved-binary md5 — 1444034d3af09fb18ef341b1fe6e8886 on devgpu004 (release release; canonical content invariant = patch-id 8fc3493dbe2655a2d15e6aa6ec4a7901cfada9b2) (d) build-env compatibility — cmake 4.3.2 at $HOME/.local/bin/cmake, NOT in default login PATH; export required before scripts/build_phoenix.sh 4-step fallback procedure: (Step 0) confirm decay (Step 1) re-transport patches if missing (Step 2) reset+re-apply if working tree corrupt (Step 3) alt-host spawn requiring Alex coordination. Substrate-spawn-analysis acknowledged structurally circular per pythia python#354(1) — fallback value is procedural readiness, not autonomous unblock (supervisor 13:07:53Z disposition: acceptable scope). Codification batch with handle-namespace + ARM64 vanilla canon per supervisor 15:05:16Z dispatch.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters