Message403412
Correct; 3.7 and 3.8 are both in security-fix-only maintenance mode; their documentation is no longer updated unless a security-related fix causes a significant change in behavior that needs to be documented.
As far as fixing this issue, we have a few options. The cause is that the source for these rows looks like ':keyword:`await` ``x``', which basically produces two inline code blocks with a non-code space between, which the pydoc-topics renderer renders as two separately quoted words.
Option 1: Replace ':keyword:`await` ``x``' with `:keyword:`await x <await>`. This keeps the link to the `await` anchor, but extends it across the ' x' bit. The pydoc rendering is '"await x"'.
Option 2: Replace ':keyword:`await` ``x``' with '``await x``. This also gives the pydoc rendering of '"await x"', but loses the link to the `await` anchor, which I would rather not do.
Option 3: As option 2, but also replace 'Await' in the description column with a link to the `await` anchor. This breaks from how other keywords in the table are linked.
Option 4: Adjust the pydoc-topics renderer to smush together consecutive inline code blocks. This might cause some issues elsewhere. |
|
Date |
User |
Action |
Args |
2021-10-07 14:00:00 | zach.ware | set | recipients:
+ zach.ware, docs@python, veky, MFH |
2021-10-07 14:00:00 | zach.ware | set | messageid: <1633615200.8.0.691129502677.issue45393@roundup.psfhosted.org> |
2021-10-07 14:00:00 | zach.ware | link | issue45393 messages |
2021-10-07 14:00:00 | zach.ware | create | |
|