Georg Brandl added the comment:
I don't think this is necessary.
--
nosy: +georg.brandl
resolution: - works for me
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15863
Terry J. Reedy added the comment:
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
Andrew Svetlov added the comment:
Well, the patch is welcome.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15863
___
___
Python-bugs-list
Andrew Svetlov added the comment:
Hash randomization is security patch.
It is applied to 2.6.8, 2.7.3, 3.2.3 and 3.3.
Python doc should not enumerate all affected releases.
For example, if you read docs for 2.6 branch it shows you 2.6.8 version only
and that's ok.
--
nosy: +asvetlov
Alexander Konovalenko added the comment:
Andrew, I don't get it. :( Why not?
The docs for Python 2.7 generally inform the reader in which Python version
every feature appeared. That's really helpful if your code should run on
earlier version of Python. You don't have to dig through the docs
Andrew Svetlov added the comment:
Well, I can try to make patch.
Please note: versionadded tag accepts only single version argument, you have to
use couple of tags which looks weird.
--
___
Python tracker rep...@bugs.python.org
New submission from Alexander Konovalenko:
Some security fixes and bug fixes that are simultaneously issued for multiple
Python versions require changes to the documentation. I'm now looking at the
hash randomization vulnerability that was fixed in 2.6.8 and 2.7.3.
The docs always mention the
