Re: [Python-Dev] docs.python.org pointing to Python 3 by default?

On Mon, May 21, 2012 at 4:32 PM, Benjamin Peterson wrote: > 2012/5/20 Nick Coghlan : >> On Mon, May 21, 2012 at 3:47 PM, Terry Reedy wrote: >>> On 5/21/2012 12:28 AM, Nick Coghlan wrote: On Mon, May 21, 2012 at 11:23 AM, Guido van Rossum  wrote: > > I suggest that we add a

Re: [Python-Dev] docs.python.org pointing to Python 3 by default?

>>> Namespaces are a great idea, let's do more of those :) >> A subdomain isn't a namespace? > A subdomain is only a namespace if you use it as one. The following > would be using docs.python.org as a namespace (and is what I think we > should move towards): > > docs.python.org/latest > docs.pyth

Re: [Python-Dev] docs.python.org pointing to Python 3 by default?

Nick Coghlan writes: > > A subdomain isn't a namespace? > > A subdomain is only a namespace if you use it as one. The following > would be using docs.python.org as a namespace (and is what I think we > should move towards): +1 > The following is *not* using it as a namespace: > > docs.

Re: [Python-Dev] PEP 420 - dynamic path computation is missing rationale

On 5/20/2012 9:33 PM, Guido van Rossum wrote: > Generally speaking the PEP is a beacon if clarity. But I stumbled > about one feature that bothers me in its specification and through its > lack of rationale. This is the section on Dynamic Path Computation: > (http://www.python.org/dev/peps/pep-0420

Re: [Python-Dev] docs.python.org pointing to Python 3 by default?

On 21 May 2012 08:35, Hynek Schlawack wrote: > Also -1 on docs3, that would suggest that it’s still something special > and 2 (= docs) is the real deal. Good point. Paul. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/l

Re: [Python-Dev] docs.python.org pointing to Python 3 by default?

On Mon, May 21, 2012 at 01:47:50AM -0400, Terry Reedy wrote: > What might be useful is to have the 'Other versions' links on the left > margin of *every* page, not just the front page, but have them link to > the corresponding page of the other docs (if there is one, and > non-trivial I expect)

Re: [Python-Dev] docs.python.org pointing to Python 3 by default?

Wiadomość napisana przez Nick Coghlan w dniu 21 maj 2012, o godz. 09:24: > The following > would be using docs.python.org as a namespace (and is what I think we > should move towards): > > docs.python.org/latest > docs.python.org/dev > docs.python.org/3.2 > docs.python.org/3.1 > docs.python.org/2

Re: [Python-Dev] docs.python.org pointing to Python 3 by default?

On Mon, 21 May 2012 14:28:06 +1000 Nick Coghlan wrote: > On Mon, May 21, 2012 at 11:23 AM, Guido van Rossum wrote: > > I suggest that we add a separate (virtual) subdomain, e.g. docs3.python.org. > > Rather than a new subdomain, I'd prefer to see a discreet > "documentation version" CSS widget,

Re: [Python-Dev] docs.python.org pointing to Python 3 by default?

On 05/21/2012 03:23 AM, Guido van Rossum wrote: > I suggest that we add a separate (virtual) subdomain, e.g. docs3.python.org. Here are the time machine keys: this subdomain has existed for a few years now :) Georg ___ Python-Dev mailing list Python-D

Re: [Python-Dev] dir() in inspect.py ?

On 21.05.12 07:52, Stefano Taschini wrote: On 21 May 2012 03:36, Guido van Rossum > wrote: [...] I have to agree with Christian that inspect.py is full of hacks and heuristics that would be fine in a module that's part of a user's app or even in a librar

Re: [Python-Dev] docs.python.org pointing to Python 3 by default?

On 18.05.12 21:30, Brian Curtin wrote: On May 18, 2012 1:26 PM, "Barry Warsaw" mailto:ba...@python.org>> wrote: > At what point should we cut over docs.python.org to point to the Python 3 > documentation by default? Today sounds good to me. Yesterday. ;-) Issue14469

Re: [Python-Dev] docs.python.org pointing to Python 3 by default?

On 05/21/2012 11:09 AM, Łukasz Langa wrote: > Wiadomość napisana przez Nick Coghlan w dniu 21 maj 2012, o godz. 09:24: > >> The following >> would be using docs.python.org as a namespace (and is what I think we >> should move towards): >> >> docs.python.org/latest >> docs.python.org/dev >> docs.p

Re: [Python-Dev] docs.python.org pointing to Python 3 by default?

On Mon, 21 May 2012 11:41:29 +0200, Georg Brandl wrote: > On 05/21/2012 03:23 AM, Guido van Rossum wrote: > > I suggest that we add a separate (virtual) subdomain, e.g. docs3.python.org. > > Here are the time machine keys: this subdomain has existed for a few years > now :) The fact that none o

Re: [Python-Dev] docs.python.org pointing to Python 3 by default?

On Mon, May 21, 2012 at 9:42 PM, Georg Brandl wrote: > Apart from the "latest" one, all these URLs already work. Yeah, I was just extending the scheme I already knew existed :) > Of course, /2.7 is redirected to /, and /3.3 to /dev, etc. > If required, the direction of these redirects can be cha

Re: [Python-Dev] docs.python.org pointing to Python 3 by default?

On Sun, May 20, 2012 at 10:47 PM, Terry Reedy wrote: > On 5/21/2012 12:28 AM, Nick Coghlan wrote: >> >> On Mon, May 21, 2012 at 11:23 AM, Guido van Rossum >>  wrote: >>> >>> I suggest that we add a separate (virtual) subdomain, e.g. >>> docs3.python.org. > > > I was about to post the exact same id

Re: [Python-Dev] PEP 420 - dynamic path computation is missing rationale

On Mon, May 21, 2012 at 1:00 AM, Eric V. Smith wrote: > On 5/20/2012 9:33 PM, Guido van Rossum wrote: >> Generally speaking the PEP is a beacon if clarity. But I stumbled >> about one feature that bothers me in its specification and through its >> lack of rationale. This is the section on Dynamic

[Python-Dev] ossaudiodev and linuxaudiodev not built on SLES11SP2 due to change in sys.platform

I am currently working on porting our Linux tool chains to SuSe Enterprise Linux 11 service pack 2 (SLES11SP2). During this process, we noticed an issue due to a change in the sys.platform string. Previously, the string was "linux2" and it has now changed to "linux3". This seems to be due to

Re: [Python-Dev] ossaudiodev and linuxaudiodev not built on SLES11SP2 due to change in sys.platform

Sorry, I forgot to mention that this is for Python 2.6.8 and 2.7.3. From: python-dev-bounces+kristofer.wempa=sig@python.org [mailto:python-dev-bounces+kristofer.wempa=sig@python.org] On Behalf Of Wempa, Kristofer Sent: Monday, May 21, 2012 10:49 AM To: python-dev@python.org Subject: [P

Re: [Python-Dev] ossaudiodev and linuxaudiodev not built on SLES11SP2 due to change in sys.platform

Am 21.05.2012 16:53, schrieb Wempa, Kristofer: > Sorry, I forgot to mention that this is for Python 2.6.8 and 2.7.3. You must be mistaken, Python 2.7.3 has a fix for the issue. configure checks for linux*: linux*) MACHDEP="linux2";; On the other hand Python 2.6.8 has no such fix and thus sets

Re: [Python-Dev] docs.python.org pointing to Python 3 by default?

On Fri, 2012-05-18 at 14:24 -0400, Barry Warsaw wrote: > At what point should we cut over docs.python.org to point to the Python 3 > documentation by default? Wouldn't this be an easy bit to flip in order to > promote Python 3 more better? If we do, perhaps we should revisit http://bugs.python.or

Re: [Python-Dev] docs.python.org pointing to Python 3 by default?

On 05/21/2012 02:14 PM, R. David Murray wrote: > On Mon, 21 May 2012 11:41:29 +0200, Georg Brandl wrote: >> On 05/21/2012 03:23 AM, Guido van Rossum wrote: >> > I suggest that we add a separate (virtual) subdomain, e.g. >> > docs3.python.org. >> >> Here are the time machine keys: this subdomain

Re: [Python-Dev] docs.python.org pointing to Python 3 by default?

On May 20, 2012, at 04:27 PM, Raymond Hettinger wrote: >When there is more uptake of Python 3, it would be reasonable move. How do we measure this, and what's the milestone for enough uptake to make the switch? Cheers, -Barry signature.asc Description: PGP signature ___

Re: [Python-Dev] docs.python.org pointing to Python 3 by default?

On 5/21/2012 3:35 AM, Hynek Schlawack wrote: Also -1 on docs3, that would suggest that it’s still something special and 2 (= docs) is the real deal. Guido and I are proposing docs2 and docs3 each pointing to the latest docs for each series. That puts them on equal status. docs.python.org, be

Re: [Python-Dev] docs.python.org pointing to Python 3 by default?

On 5/21/2012 3:24 AM, Nick Coghlan wrote: docs.python.org/latest docs.python.org/dev docs.python.org/3.2 docs.python.org/3.1 docs.python.org/2.7 docs.python.org/2.6 etc... This looks great except for 'latest', which is ambiguous and awkward. Like Guido, I would have docs2 and docs3 link to th

Re: [Python-Dev] docs.python.org pointing to Python 3 by default?

On Mon, 21 May 2012 12:03:31 -0400 Terry Reedy wrote: > On 5/21/2012 3:24 AM, Nick Coghlan wrote: > > > docs.python.org/latest > > docs.python.org/dev > > docs.python.org/3.2 > > docs.python.org/3.1 > > docs.python.org/2.7 > > docs.python.org/2.6 > > etc... > > This looks great except for 'lates

Re: [Python-Dev] docs.python.org pointing to Python 3 by default?

On May 21, 2012, at 02:28 PM, Nick Coghlan wrote: >Rather than a new subdomain, I'd prefer to see a discreet >"documentation version" CSS widget, similar to that used in the Django >docs (see https://docs.djangoproject.com/en/1.4/) that indicated the >current displayed version and provided quick l

Re: [Python-Dev] docs.python.org pointing to Python 3 by default?

On 5/21/2012 7:42 AM, Georg Brandl wrote: On 05/21/2012 11:09 AM, Łukasz Langa wrote: Wiadomość napisana przez Nick Coghlan w dniu 21 maj 2012, o godz. 09:24: The following would be using docs.python.org as a namespace (and is what I think we should move towards): docs.python.org/latest docs.

Re: [Python-Dev] docs.python.org pointing to Python 3 by default?

On Mon, 21 May 2012 11:19:56 -0400, David Malcolm wrote: > On Fri, 2012-05-18 at 14:24 -0400, Barry Warsaw wrote: > > At what point should we cut over docs.python.org to point to the Python 3 > > documentation by default? Wouldn't this be an easy bit to flip in order to > > promote Python 3 more

Re: [Python-Dev] docs.python.org pointing to Python 3 by default?

>> Also -1 on docs3, that would suggest that it’s still something special >> and 2 (= docs) is the real deal. > Guido and I are proposing docs2 and docs3 each pointing to the latest > docs for each series. That puts them on equal status. > docs.python.org, besides being a namespace for specific ver

Re: [Python-Dev] cpython: Close #13585: add contextlib.ExitStack to replace the ill-fated

Am 21.05.2012 14:54, schrieb nick.coghlan: > http://hg.python.org/cpython/rev/8ef66c73b1e1 > changeset: 77095:8ef66c73b1e1 > user:Nick Coghlan > date:Mon May 21 22:54:43 2012 +1000 > summary: > Close #13585: add contextlib.ExitStack to replace the ill-fated > contextlib.nested

Re: [Python-Dev] cpython (3.2): #14766: Add correct algorithm for when a 'time' object is naive.

Am 15.05.2012 04:33, schrieb r.david.murray: > diff --git a/Doc/library/datetime.rst b/Doc/library/datetime.rst > --- a/Doc/library/datetime.rst > +++ b/Doc/library/datetime.rst > @@ -15,16 +15,23 @@ > formatting and manipulation. For related > functionality, see also the :mod:`time` and :mod:`c

Re: [Python-Dev] docs.python.org pointing to Python 3 by default?

Le 21/05/2012 07:42, Georg Brandl a écrit : > What about: > > * Canonical: > > docs.python.org/2/ > docs.python.org/3/ > > for latest versions of 2.x and 3.x > > docs.python.org/2.7/ etc. > > for latest minor versions > > docs.python.org/dev/ > > for latest dev version. +1. I’d be +1 to add

Re: [Python-Dev] docs.python.org pointing to Python 3 by default?

On 5/21/2012 11:50 AM, Georg Brandl wrote: On 05/21/2012 02:14 PM, R. David Murray wrote: On Mon, 21 May 2012 11:41:29 +0200, Georg Brandl wrote: On 05/21/2012 03:23 AM, Guido van Rossum wrote: I suggest that we add a separate (virtual) subdomain, e.g. docs3.python.org. Here are the time m

Re: [Python-Dev] PEP 420 - dynamic path computation is missing rationale

On Mon, May 21, 2012 at 9:55 AM, Guido van Rossum wrote: > Ah, I see. But I disagree that this is a reasonable constraint on > sys.path. The magic __path__ object of a toplevel namespace module > should know it is a toplevel module, and explicitly refetch sys.path > rather than just keeping aroun

Re: [Python-Dev] cpython: Close #14588: added a PEP 3115 compliant dynamic type creation mechanism

Am 19.05.2012 18:34, schrieb nick.coghlan: > diff --git a/Doc/library/types.rst b/Doc/library/types.rst > --- a/Doc/library/types.rst > +++ b/Doc/library/types.rst > @@ -1,5 +1,5 @@ > -:mod:`types` --- Names for built-in types > -= > +:mod:`types` --- Dynami

Re: [Python-Dev] cpython (3.2): Issue12541 - Add UserWarning for unquoted realms

Am 15.05.2012 18:08, schrieb senthil.kumaran: > diff --git a/Lib/urllib/request.py b/Lib/urllib/request.py > --- a/Lib/urllib/request.py > +++ b/Lib/urllib/request.py > @@ -95,6 +95,7 @@ > import sys > import time > import collections > +import warnings > > from urllib.error import URLError,

[Python-Dev] Volunteering to be PEP czar for PEP 421, sys.implementation

I've mentioned this in private to a few folks, with generally positive feedback. I am formally volunteering to be PEP czar for PEP 421, sys.implementation. If there are no objections in the next few days, I'll make it official. Cheers, -Barry signature.asc Description: PGP signature __

Re: [Python-Dev] PEP 420 - dynamic path computation is missing rationale

As a simple example to back up PJE's explanation, consider: 1. encodings becomes a namespace package 2. It sometimes gets imported during interpreter startup to initialise the standard io streams 3. An application modifies sys.path after startup and wants to contribute additional encodings Search

Re: [Python-Dev] PEP 420 - dynamic path computation is missing rationale

I agree the parent path should be retrieved by name rather than a direct reference when checking the cache validity, though. -- Sent from my phone, thus the relative brevity :) ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mail

Re: [Python-Dev] PEP 420 - dynamic path computation is missing rationale

On 5/21/2012 2:08 PM, PJ Eby wrote: > On Mon, May 21, 2012 at 9:55 AM, Guido van Rossum > wrote: > > Ah, I see. But I disagree that this is a reasonable constraint on > sys.path. The magic __path__ object of a toplevel namespace module > should know it is a to