Message 183943 - Python tracker

➜

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	ncoghlan
Recipients	barry, brandon-rhodes, brett.cannon, docs@python, georg.brandl, ncoghlan, onelson, terry.reedy
Date	2013-03-11.08:08:15
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1362989296.23.0.767182983412.issue17370@psf.upfronthosting.co.za>
In-reply-to

Content
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.

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.

History
Date	User	Action	Args
2013-03-11 08:08:16	ncoghlan	set	recipients: + ncoghlan, barry, brett.cannon, georg.brandl, terry.reedy, brandon-rhodes, docs@python, onelson
2013-03-11 08:08:16	ncoghlan	set	messageid: <1362989296.23.0.767182983412.issue17370@psf.upfronthosting.co.za>
2013-03-11 08:08:16	ncoghlan	link	issue17370 messages
2013-03-11 08:08:15	ncoghlan	create