Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit dfe0e30

Browse files
[3.13] Docs: Fix markups for emphasis (GH-135598) (GH-135686)
Docs: Fix markups for emphasis (GH-135598) The word emphasis character `_` is not supported as sphinx markup, so changed to `*`. (cherry picked from commit 46c60e0) Co-authored-by: Yuki Kobayashi <[email protected]>
1 parent a0a1aa3 commit dfe0e30

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

Doc/c-api/refcounting.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -201,7 +201,7 @@ of Python objects.
201201
202202
Py_SETREF(dst, src);
203203
204-
That arranges to set *dst* to *src* _before_ releasing the reference
204+
That arranges to set *dst* to *src* *before* releasing the reference
205205
to the old value of *dst*, so that any code triggered as a side-effect
206206
of *dst* getting torn down no longer believes *dst* points
207207
to a valid object.

Doc/library/logging.config.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -586,7 +586,7 @@ configuration dictionary for the handler named ``foo``, and later (once that
586586
handler has been configured) it points to the configured handler instance.
587587
Thus, ``cfg://handlers.foo`` could resolve to either a dictionary or a handler
588588
instance. In general, it is wise to name handlers in a way such that dependent
589-
handlers are configured _after_ any handlers they depend on; that allows
589+
handlers are configured *after* any handlers they depend on; that allows
590590
something like ``cfg://handlers.foo`` to be used in configuring a handler that
591591
depends on handler ``foo``. If that dependent handler were named ``bar``,
592592
problems would result, because the configuration of ``bar`` would be attempted

0 commit comments

Comments
 (0)