➜

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 belopolsky
Recipients belopolsky, docs@python, eric.araujo, georg.brandl, ron_adam
Date 2010-11-18.05:03:18
SpamBayes Score 4.7748276e-06
Marked as misclassified No
Message-id <AANLkTim6Hg5aXZ-UG=SQRizU_rZxHiDWLcFe-r5dF9Yj@mail.gmail.com>
In-reply-to <1290054405.25.0.390821249675.issue10446@psf.upfronthosting.co.za>
Content 
On Wed, Nov 17, 2010 at 11:26 PM, Éric Araujo <report@bugs.python.org> wrote:
..
>> If there was say latest/X.Y, I would use that.  Wait -
>> there is: docs.python.org/X.Y.  Would you prefer that?
> My point was that people used 2.7 docs even when developing for 2.6.

The point of this bug report was that 3.x pydoc was sending users to
2.7, which is clearly unacceptable. 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.

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?
History
Date User Action Args
2010-11-18 05:03:20belopolskysetrecipients: + belopolsky, georg.brandl, ron_adam, eric.araujo, docs@python
2010-11-18 05:03:18belopolskylinkissue10446 messages
2010-11-18 05:03:18belopolskycreate