Mark up of references in different form (issue 27036)
https://bugs.python.org/review/27036/diff/17256/Doc/library/asyncore.rst File Doc/library/asyncore.rst (right): https://bugs.python.org/review/27036/diff/17256/Doc/library/asyncore.rst#new... Doc/library/asyncore.rst:104: :c:func:`polled <poll>` for read and write events. Would it hurt to just drop the markup? As far as I know it normally just changes the font, and doesn’t make a link. https://bugs.python.org/review/27036/diff/17256/Doc/library/email.headerregi... File Doc/library/email.headerregistry.rst (right): https://bugs.python.org/review/27036/diff/17256/Doc/library/email.headerregi... Doc/library/email.headerregistry.rst:214: ``decoded`` value is set by :attr:`joining <~str.join>` the :class:`str` value of I think you would have to drop the tilde (~) to get the link to work. There are other changes that also have this problem. But I don’t like this version any better than the original. What about something like: . . . is set to the concatenation of the :class:`str` value of each element . . ., using :meth:`str.join` and a separator of ``', '``. https://bugs.python.org/review/27036/diff/17256/Doc/whatsnew/3.4.rst File Doc/whatsnew/3.4.rst (right): https://bugs.python.org/review/27036/diff/17256/Doc/whatsnew/3.4.rst#newcode... Doc/whatsnew/3.4.rst:1116: mmap objects can now be :mod:`weakrefed <weakref>`. (Contributed by Valerie Lambert in Should probably be spelt “weakreffed” (refed means re-fed as in fed again) Maybe “weakly referenced with :mod:`weakref` ”, or similar? https://bugs.python.org/review/27036/
participants (1)
-
vadmium+py@gmail.com