[3.14] gh-154753: Update references to moved files in the docs (GH-155553) (#155810)
StanFromIreland <[email protected]>
| Newsgroups | gmane.comp.python.cvs |
|---|---|
| Message-ID | <[email protected]> |
https://github.com/python/cpython/commit/b104b74ecfedf62b718175cdca62f3720f5f22f5 commit: b104b74ecfedf62b718175cdca62f3720f5f22f5 branch: 3.14 author: Bhuvansh <[email protected]> committer: StanFromIreland <[email protected]> date: 2026-08-16T21:48:03+01:00 summary: [3.14] gh-154753: Update references to moved files in the docs (GH-155553) (#155810) Co-authored-by: Stan Ulbrych <[email protected]> files: M Doc/extending/extending.rst M Doc/library/sys.rst M InternalDocs/code_objects.md M InternalDocs/jit.md diff --git a/Doc/extending/extending.rst b/Doc/extending/extending.rst index 23e0064c6c93609..6518e20cafbc9e7 100644 --- a/Doc/extending/extending.rst +++ b/Doc/extending/extending.rst @@ -1405,7 +1405,7 @@ Finally it should be mentioned that Capsules offer additional functionality, which is especially useful for memory allocation and deallocation of the pointer stored in a Capsule. The details are described in the Python/C API Reference Manual in the section :ref:`capsules` and in the implementation of Capsules (files -:file:`Include/pycapsule.h` and :file:`Objects/pycapsule.c` in the Python source +:file:`Include/pycapsule.h` and :file:`Objects/capsule.c` in the Python source code distribution). .. rubric:: Footnotes diff --git a/Doc/library/sys.rst b/Doc/library/sys.rst index 9078af7cac78d61..6fe097407445e49 100644 --- a/Doc/library/sys.rst +++ b/Doc/library/sys.rst @@ -1798,7 +1798,7 @@ always available. Unless explicitly noted otherwise, all variables are read-only The interpreter is about to execute a new line of code or re-execute the condition of a loop. The local trace function is called; *arg* is ``None``; the return value specifies the new local trace function. See - :file:`Objects/lnotab_notes.txt` for a detailed explanation of how this + :source:`InternalDocs/code_objects.md` for a detailed explanation of how this works. Per-line events may be disabled for a frame by setting :attr:`~frame.f_trace_lines` to :const:`False` on that diff --git a/InternalDocs/code_objects.md b/InternalDocs/code_objects.md index a91a7043c1b8d41..7df1fe9fc2e25db 100644 --- a/InternalDocs/code_objects.md +++ b/InternalDocs/code_objects.md @@ -48,7 +48,7 @@ Note that traceback objects don't store all this information -- they store the s number, for backward compatibility, and the "last instruction" value. The rest can be computed from the last instruction (`tb_lasti`) with the help of the locations table. For Python code, there is a convenience method -(`codeobject.co_positions`)[https://docs.python.org/dev/reference/datamodel.html#codeobject.co_positions] +[`codeobject.co_positions`](https://docs.python.org/dev/reference/datamodel.html#codeobject.co_positions) which returns an iterator of `({line}, {endline}, {column}, {endcolumn})` tuples, one per instruction. There is also `co_lines()` which returns an iterator of `({start}, {end}, {line})` tuples, diff --git a/InternalDocs/jit.md b/InternalDocs/jit.md index 095853807377a45..2f6d8c411bdb7d6 100644 --- a/InternalDocs/jit.md +++ b/InternalDocs/jit.md @@ -115,7 +115,7 @@ template file [`Tools/jit/template.c`](../Tools/jit/template.c). Each of the `.c` files is compiled by LLVM, to produce an object file that contains a function that executes the opcode. These compiled functions are used to generate the file -[`jit_stencils.h`](../jit_stencils.h), which contains the functions +`jit_stencils.h`, which contains the functions that the JIT can use to emit code for each of the bytecodes. For Python maintainers this means that changes to the bytecodes and _______________________________________________ Python-checkins mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3//lists/python-checkins.python.org Member address: [email protected]