On Aug 28, 2010, at 01:12 AM, Georg Brandl wrote:
>I don't think I'll want to bother with porting doc fixes to the 2.6
>branch.
Thanks for the feedback everyone. We will not be porting doc fixes to
release26-maint. I would be open to a doc fix that was specifically
addressing a security concern
> Regards, and a toast to 2.6.6!
Prost!
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Thanks everyone for the feedback. I think my question has got good
answers (usage patterns, versionchanged/versionadded, lack of releases,
opinion of the doc editor), so it seems good for our users and for
developers to let the 2.6 docs in peace.
Regards, and a toast to 2.6.6!
Am 25.08.2010 17:32, schrieb Éric Araujo:
>> The question really is whether there is any chance that they will get
>> released, in some form. There won't be further binary releases (at least
>> not from python.org), so there definitely won't be a CHM release.
>
> I think that the most important re
> I like how the django project present their documentation: there is
> a little informational text at the head of each doc, saying that
> "you're not browsing the most up-to-date documentation, you can
> find the last one here"; maybe can we do a similar thing for the python
> doc ?
In principle,
Le 08/25/2010 05:32 PM, Éric Araujo a écrit :
> I think that the most important release is docs.python.org/2.6,
> regardless of python.org/OS-specific downloadable doc packages.
>
> If people do like haypo and use the most recent docs instead of the
> version-specific ones, there’s indeed no need
> The question really is whether there is any chance that they will get
> released, in some form. There won't be further binary releases (at least
> not from python.org), so there definitely won't be a CHM release.
I think that the most important release is docs.python.org/2.6,
regardless of pytho
> OTOH, I suspect there won't be *that* many documentation fixes for Python 2.6
> and that the overhead will be minimal. What did we do for Python 2.5?
The question really is whether there is any chance that they will get
released, in some form. There won't be further binary releases (at least
no
Le mercredi 25 août 2010 01:12:40, Barry Warsaw a écrit :
> merwok asks on IRC whether documentation changes to release26-maint will be
> allowed. I can sympathize with the 'allow' argument; Python 2.6 is still
> either the default version or soon to be the new default in several
> distributions,
On Aug 24, 2010, at 03:31 PM, Barry Warsaw wrote:
>Python 2.6.6 marks the end of regular maintenance releases for the
>Python 2.6 series. From now until October 2013, only security
>related, source-only releases of Python 2.6 will be made available.
>After that date, Python 2.6 will no longer be
On Aug 24, 2010, at 12:31 PM, Barry Warsaw wrote:
> Hello fellow Pythoneers and Pythonistas,
>
> I'm very happy to announce the release of Python 2.6.6.
Thanks Barry :-)
Raymond
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.
Hello fellow Pythoneers and Pythonistas,
I'm very happy to announce the release of Python 2.6.6. A truly impressive
number of bugs have been fixed since Python 2.6.5. Source code and Windows
installers for Python 2.6.6 are now available here:
http://www.python.org/download/releases/2.6.6/
12 matches
Mail list logo
