Mailman 3 October 2012 - Python-Dev

Acceptance of PEPs
by Brian Curtin 29 Oct '12

29 Oct '12

I just found out that PEP 430 came up again and was approved, but only because of another website. After that I looked back through my email only to find mention via python-checkins. Aren't PEPs typically acted on here on python-dev? I mention this because I was writing up a blog.python.org post about the (somewhat recent) Sphinx theme change and the change to add a version dropdown which was pushed yesterday. I was about to wrap it up and schedule it for tomorrow when I found out about 430, which I'm now including. note: I have no problems with that PEP actually being approved. I've wanted that change for 2 years.

4 3

Re: [Python-Dev] [Python-checkins] peps: PEP for updating the URL layout on docs.python.org
by Chris Jerdonek 29 Oct '12

29 Oct '12

On Sat, Oct 27, 2012 at 7:36 AM, nick.coghlan <python-checkins(a)python.org> wrote: > http://hg.python.org/peps/rev/c7ba002ca91d > changeset: 4568:c7ba002ca91d > user: Nick Coghlan <ncoghlan(a)gmail.com> > date: Sun Oct 28 00:36:36 2012 +1000 > summary: > PEP for updating the URL layout on docs.python.org > ... > +Implementation > +============== > + > +The URLs on docs.python.org are controlled by the python.org infrastructure > +team rather than through the CPython source repo, so acceptance and > +implementation of the ideas in this PEP will be up to the team. Related to this, just checking to see if anyone is taking responsibility for following up with http://www.python.org. I imagine they have several links that may no longer point to the correct version (e.g. the "Documentation" link under "Quick Links (2.7.3)" in the left column of the home page now results in http://docs.python.org/3/, and similarly for 2.x on http://www.python.org/doc/ ). --Chris

1 0

Re: [Python-Dev] [Python-checkins] peps: PEP for updating the URL layout on docs.python.org
by Chris Jerdonek 29 Oct '12

29 Oct '12

On Sun, Oct 28, 2012 at 4:34 AM, Georg Brandl <g.brandl(a)gmx.net> wrote: > Am 28.10.2012 12:29, schrieb Chris Jerdonek: > ... > I understand "latest" to mean "latest stable plus bugfixes". > I.e., /3/ is 3.3.0+. /dev and /3.4 is 3.4a0. It might need clarifying > in the PEP. > ... >> There's a slight mismatch with how we're doing it today because >> "http://docs.python.org/3/" shows 3.3.0 in the title even though it's >> the in-progress 3.3.1. The title should perhaps reflect that it's >> post 3.3.0 (and similarly for the 2.7 and 3.2 pages). > > Well, that has always been the case, and it doesn't matter anyway, because > generally there's nothing in 3.3.1, feature-wise, that won't have been in 3.3.0. One reason to change would be to avoid possible confusion created on pages like this-- http://docs.python.org/3.3/whatsnew/3.2.html where it says-- Author: Raymond Hettinger Release: 3.3.0 Date: October 27, 2012 Would there be any disadvantage to changing the in-development titles to read something like 3.3.0+, etc? --Chris

4 8

Re: [Python-Dev] [Python-ideas] docs.python.org
by Yury Selivanov 28 Oct '12

28 Oct '12

On 2012-10-28, at 3:59 AM, Georg Brandl <g.brandl(a)gmx.net> wrote: > Well, with the approval I've seen here, I have absolutely no problem > with appointing myself PEP Czar and accepting the PEP :) That's awesome! - Yury

1 0

Re: [Python-Dev] [Python-checkins] peps: PEP for updating the URL layout on docs.python.org
by Nick Coghlan 28 Oct '12

28 Oct '12

On Sun, Oct 28, 2012 at 9:34 PM, Georg Brandl <g.brandl(a)gmx.net> wrote: > Am 28.10.2012 12:29, schrieb Chris Jerdonek: >> On Sat, Oct 27, 2012 at 7:36 AM, nick.coghlan >> <python-checkins(a)python.org> wrote: >>> http://hg.python.org/peps/rev/c7ba002ca91d >>> changeset: 4568:c7ba002ca91d >>> user: Nick Coghlan <ncoghlan(a)gmail.com> >>> date: Sun Oct 28 00:36:36 2012 +1000 >>> summary: >>> PEP for updating the URL layout on docs.python.org >> >>> +* ``http://docs.python.org/x/*`` >>> +* ``http://docs.python.org/x.y/*`` >>> +* ``http://docs.python.org/release/x.y.z/*`` >>> +* ``http://docs.python.org/devguide`` >>> + >>> +The ``/x/`` URLs mean "give me the latest documentation for this release >>> +series``. Differences relative to previous versions in the release series >>> +will be available through "version added" and "version changed" markers. >>> + >>> +The ``/x.y/`` URLs mean "give me the latest documentation for this release". >> >> It might be worth clarifying what "latest" means for both the "x" and >> "x.y" forms. For example, should "http://docs.python.org/3/" today >> link to the released 3.3.0 version, the in-progress 3.3.1 version, or >> the in-progress 3.4.0? > > I understand "latest" to mean "latest stable plus bugfixes". > I.e., /3/ is 3.3.0+. /dev and /3.4 is 3.4a0. It might need clarifying > in the PEP. Yes, I realised last night that it would be good to be more explicit about this. The "release" hierarchy should be for versions exactly as they were released, while the shorter ones draw directly from source control (and thus may contain fixes which otherwise haven't been released yet). I updated the PEP to describe what Georg has put in place more explicitly (initially I was going to propose a change to the way /dev/ URLs are handled, but then I realised what is already there made more sense). Cheers, Nick. -- Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia

1 0

Re: [Python-Dev] cpython (merge 2.6 -> 2.7): merge with 2.6
by Antoine Pitrou 28 Oct '12

28 Oct '12

On Sun, 28 Oct 2012 08:05:00 +0100 (CET) georg.brandl <python-checkins(a)python.org> wrote: > http://hg.python.org/cpython/rev/ee33671b2c6a > changeset: 79995:ee33671b2c6a > branch: 2.7 > parent: 79983:7ca30af90c11 > parent: 79994:4a17784f2fee > user: Georg Brandl <georg(a)python.org> > date: Sun Oct 28 08:06:11 2012 +0100 > summary: > merge with 2.6 > > files: > Doc/tools/sphinxext/static/version_switch.js | 18 +++++---- > 1 files changed, 10 insertions(+), 8 deletions(-) Is it deliberate for our Javascript code to use 2-space indents? Regards Antoine.

2 1

Re: [Python-Dev] [Python-checkins] peps: PEP for updating the URL layout on docs.python.org
by Chris Jerdonek 28 Oct '12

28 Oct '12

On Sat, Oct 27, 2012 at 7:36 AM, nick.coghlan <python-checkins(a)python.org> wrote: > http://hg.python.org/peps/rev/c7ba002ca91d > changeset: 4568:c7ba002ca91d > user: Nick Coghlan <ncoghlan(a)gmail.com> > date: Sun Oct 28 00:36:36 2012 +1000 > summary: > PEP for updating the URL layout on docs.python.org > +* ``http://docs.python.org/x/*`` > +* ``http://docs.python.org/x.y/*`` > +* ``http://docs.python.org/release/x.y.z/*`` > +* ``http://docs.python.org/devguide`` > + > +The ``/x/`` URLs mean "give me the latest documentation for this release > +series``. Differences relative to previous versions in the release series > +will be available through "version added" and "version changed" markers. > + > +The ``/x.y/`` URLs mean "give me the latest documentation for this release". It might be worth clarifying what "latest" means for both the "x" and "x.y" forms. For example, should "http://docs.python.org/3/" today link to the released 3.3.0 version, the in-progress 3.3.1 version, or the in-progress 3.4.0? For the "x" form, I think we mean the second because that is what it points to today, i.e. the in-development version of the highest released minor version of the major version "x". There's a slight mismatch with how we're doing it today because "http://docs.python.org/3/" shows 3.3.0 in the title even though it's the in-progress 3.3.1. The title should perhaps reflect that it's post 3.3.0 (and similarly for the 2.7 and 3.2 pages). --Chris

1 0

Re: [Python-Dev] devguide: Silence Sphinx warning
by Georg Brandl 28 Oct '12

28 Oct '12

Am 19.10.2012 14:06, schrieb nick.coghlan: > http://hg.python.org/devguide/rev/08f963e19a3e > changeset: 559:08f963e19a3e > user: Nick Coghlan <ncoghlan(a)gmail.com> > date: Fri Oct 19 22:06:19 2012 +1000 > summary: > Silence Sphinx warning > > files: > setup.rst | 2 +- > 1 files changed, 1 insertions(+), 1 deletions(-) > > > diff --git a/setup.rst b/setup.rst > --- a/setup.rst > +++ b/setup.rst > @@ -184,7 +184,7 @@ > ''''''' > > **Python 3.3** and later use Microsoft Visual Studio 2010. You can > -download Microsoft Visual C++ 2010 Express `here > +download Microsoft Visual C++ 2010 Express `from Microsoft's site > <http://www.microsoft.com/visualstudio/en-us/products/2010-editions/visual-c…>`_. JFTR, this is a Docutils warning, not a Sphinx warning, and can also be avoided by using `...`__ (i.e. two underscores). The one-underscore form creates a "target" that you can then reference again from elsewhere; the two-underscore form doesn't. cheers, Georg

2 1

Re: [Python-Dev] [Python-ideas] docs.python.org
by Nick Coghlan 28 Oct '12

28 Oct '12

On Sun, Oct 28, 2012 at 5:59 PM, Georg Brandl <g.brandl(a)gmx.net> wrote: > Am 27.10.2012 16:40, schrieb Nick Coghlan: > >>>> 4. We add a notice like the one above to the home page of the 2.7 >>>> docs, announce it on the PSF blog, announce it far and wide >>> >>> We also need a solution for URLs that exist for Python 2, but >>> not for Python 3. Those should be redirected to the Python 2 >>> resource automatically, e.g. URLs pointing to the Python 2 modules >>> that were renamed in Python 3. >>> >>> BTW: Will you write up a PEP for this ? >> >> Committed as PEP 430, should show up >> http://www.python.org/dev/peps/pep-0430 before too long. > > Well, with the approval I've seen here, I have absolutely no problem > with appointing myself PEP Czar and accepting the PEP :) Heh, asking you to do that was next on my list, so thanks. Did Guido hide a mind reading device in the time machine? :) > I'll work on fixing the Apache config. Huzzah \o/ Cheers, Nick. -- Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia

1 0

Re: [Python-Dev] [Python-checkins] peps: PEP 430 is Final.
by Barry Warsaw 28 Oct '12

28 Oct '12

On Oct 28, 2012, at 09:21 AM, georg.brandl wrote: > PEP 430 is Final. From the PEP: "The existing /py3k/ subpath would be remapped to the new /3/ subpath." Does "remapped" mean redirects so as not to break the existing py3k urls? If so, then cool. Cheers, -Barry

2 1