➜

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 eric.araujo
Recipients belopolsky, docs@python, eric.araujo, georg.brandl, ron_adam
Date 2010-11-18.05:06:40
SpamBayes Score 0.00020483042
Marked as misclassified No
Message-id <1290056802.56.0.308564936698.issue10446@psf.upfronthosting.co.za>
In-reply-to
Content 
> The point of this bug report was that 3.x pydoc was sending users to
> 2.7, which is clearly unacceptable.
Agreed.  My reply about x.y vs. x.y+1 was a reaction to your patch, not a misunderstanding of the point of this bug.

> As long as documentation bug fixes are backported to maintenance
> branches, I don't see an advantage in consulting 3.2 when developing for 3.1.
I prefer version-specific docs too, but the thread on python-dev seemed to show I was not in the majority.

> Now, I keep this issue open to decide if we should backport this to
> 2.7 where this is not a bug (yet), but will be when default docs
> switch to 3.x.  What do you think?
+1 for backporting.
History
Date User Action Args
2010-11-18 05:06:42eric.araujosetrecipients: + eric.araujo, georg.brandl, belopolsky, ron_adam, docs@python
2010-11-18 05:06:42eric.araujosetmessageid: <1290056802.56.0.308564936698.issue10446@psf.upfronthosting.co.za>
2010-11-18 05:06:40eric.araujolinkissue10446 messages
2010-11-18 05:06:40eric.araujocreate