[issue17370] PEP should note related PEPs
Nick Coghlan added the comment: Yeah, I think the problem in this case is specific to the multi-versioned PEPs like the WSGI reference and the metadata standards. In that case, a separate section in the document itself seems more appropriate than a generic header field. We should consider a similar section for PEP 302 (pointing to the 3.3 language reference) given the length of time that PEP has been the only systematic documentation for the import hooks. -- nosy: +ncoghlan ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17370 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17370] PEP should note related PEPs
Barry A. Warsaw added the comment: It seems to me that the right thing to add a related PEPs section to any PEP which needs it, but I don't think we need an official header for it. Thus, I'm closing this PEP as Won't Fix. Feel free to open new bugs for any specific PEP that needs additional work, or if you have commit privileges, JFDI. :) -- resolution: - wont fix status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17370 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17370] PEP should note related PEPs
Terry J. Reedy added the comment: Re-reading the original post, I see that a section (or paragraph) was an option Brandon requested. Changed title to reflect remaining issue. -- title: PEP should note if it has been superseded - PEP should note related PEPs ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17370 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
