This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ezio.melotti
Recipients barry, brett.cannon, chris.jerdonek, docs@python, eric.araujo, ezio.melotti, goodger, loewis, ncoghlan
Date 2012-11-29.04:06:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1354161971.58.0.461351526145.issue16574@psf.upfronthosting.co.za>
In-reply-to
Content
FTR the reason I suggested to modify PEP 362 is that we are linking to it from the docs.  This means that people will go and read the PEP looking for clarifications, so the PEP should be clear.  In this regard I see the PEP (or at least the relevant section) as documentation, and given that it's about an aspect of Python that is not going to change any time soon, it makes sense to get it right and keep referencing the PEP.
This doesn't normally apply to most of the other PEPs, especially if what they proposed is now documented on docs.python.org.

(On a side note, I now noticed that the parameter kinds are also documented in http://docs.python.org/dev/library/inspect.html#inspect.Parameter.kind, so we could link to that instead of linking to the PEP.)
History
Date User Action Args
2012-11-29 04:06:11ezio.melottisetrecipients: + ezio.melotti, loewis, barry, brett.cannon, goodger, ncoghlan, eric.araujo, chris.jerdonek, docs@python
2012-11-29 04:06:11ezio.melottisetmessageid: <1354161971.58.0.461351526145.issue16574@psf.upfronthosting.co.za>
2012-11-29 04:06:11ezio.melottilinkissue16574 messages
2012-11-29 04:06:11ezio.melotticreate