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 terry.reedy
Recipients alexkon, asvetlov, docs@python, terry.reedy
Date 2012-09-07.19:47:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1347047228.12.0.113779159957.issue15863@psf.upfronthosting.co.za>
In-reply-to
Content
I do not think there should be references between the Python 2 docs and Python 3 docs. But within each, I think it ok to have exceptional multiple references for what is, I believe, a unique situation: a security fix that required a new feature. Do it however seems most graceful.

My first thought was that someone seeing "added in 2.6.8' should know that adding a feature in a bugfix release is almost never done, hence it might not be in 2.7.0. But then I remembered that this fix is mainly for web sites, and the reader selecting which Python versions to use might not be a Python programmer.
History
Date User Action Args
2012-09-07 19:47:08terry.reedysetrecipients: + terry.reedy, asvetlov, docs@python, alexkon
2012-09-07 19:47:08terry.reedysetmessageid: <1347047228.12.0.113779159957.issue15863@psf.upfronthosting.co.za>
2012-09-07 19:47:07terry.reedylinkissue15863 messages
2012-09-07 19:47:07terry.reedycreate