On 14Sep2020 18:17, Terry Reedy <tjre...@udel.edu> wrote: >On 9/14/2020 5:25 AM, Cameron Simpson wrote: >>On 14Sep2020 01:16, Ned Deily <n...@python.org> wrote: >>>>I'll make some PRs. How to submit? Here, or a BPO or something? >>> >>>My suggestion would be to open one BPO issue for "adding PEP references to >>>documentation" and then creating PRs as needed against it. As you probably >>>know, the devguide has the details including for the inline markup role >>>:pep:. >>> >>>https://devguide.python.org/documenting/#rest-inline-markup
Ned, Terry, There's a PR here: https://github.com/python/cpython/pull/22269 It's associated with BPO: https://bugs.python.org/issue41787 >I agree with one master issue. I would prefer short blurb. "Add >rationale for __length_hint__ and link to PEP ###. I'm not sure this warrants a blurb. Not yet, anyway. This is a tiny PR so that we can agree on a style for mentioning the PEP. If we agree, I'm hoping to followup with a PR for each whatsnew, working backwards from 3.8, mentioning the relevant PEPs as I locate them. Unless you'd rather something more fine grained. I guess also if we agree I should patch the doc guidelines about "New in version N" lines (and changed/deprecated too, where those are PEP driven). Also, for discussion, is a separate feature in the same BPO advocating modifying "New in version V" to put a link on "version V" to reference an anchor for the whatsnew entry, or the more specific in-the-whatsnew anchors where they exist. Cheers, Cameron Simpson <c...@cskk.id.au> _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/TEJPSJS64PWTDLHU43TQEUHD7FUQMBQX/ Code of Conduct: http://python.org/psf/codeofconduct/
