Changes by Ram Rachum r...@rachum.com:
--
assignee: docs@python
components: Documentation
nosy: cool-RR, docs@python
priority: normal
severity: normal
status: open
title: List of development releases in PEPs like 429 should be links to
download pages
type: behavior
versions: Python
New submission from Benjamin Peterson:
I disagree. They are easy enough to find on the website. Easier than the
release schedule I hope! Of course, RMs are welcome to link to the download
page if they want, but we needn't require it.
--
nosy: +benjamin.peterson
resolution: - rejected
Ram Rachum added the comment:
I looked for it for 10 minutes but couldn't find the link. I ended up using a
URL from an old script. I still don't know how I was supposed to find it.
--
___
Python tracker rep...@bugs.python.org
Ned Deily added the comment:
AFAIK, traditionally, there have not been separate download pages for each
pre-release of a new feature (e.g. 3.4.0) or maintenance (e.g. 3.3.5) release.
The usual practice has been to create *one* release page at the usual URI (e.g.
