Re: [Python-Dev] cpython: Remove outdated statements about threading and imports.

2012-05-18 Thread Nick Coghlan
On May 18, 2012 11:34 PM, "Antoine Pitrou" wrote: > > On Fri, 18 May 2012 23:16:09 +1000 > Nick Coghlan wrote: > > > I know you fixed the deadlock problem, but the warnings about shutdown > > misbehaviour are still valid. > > Do we have a reproducer? It should have been fixed by > http://bugs.pyt

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

2012-05-18 Thread Terry Reedy
On 5/18/2012 2:39 PM, Hynek Schlawack wrote: Hi, 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? I’d vote for the release of 3.3 instead of a surprise change in

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

2012-05-18 Thread Barry Warsaw
On May 18, 2012, at 11:36 AM, Benjamin Peterson wrote: >2012/5/18 Barry Warsaw : >> 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? > >Perhaps on the occasion o

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

2012-05-18 Thread Hynek Schlawack
Hi, > 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? I’d vote for the release of 3.3 instead of a surprise change in the middle of nowhere. Cheers, Hynek _

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

2012-05-18 Thread Benjamin Peterson
2012/5/18 Barry Warsaw : > 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? Perhaps on the occasion on the release on Python 3.3? -- Regards, Benjamin _

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

2012-05-18 Thread Brian Curtin
On May 18, 2012 1:26 PM, "Barry Warsaw" 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. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/ma

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

2012-05-18 Thread Barry Warsaw
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? Cheers, -Barry signature.asc Description: PGP signature ___ Python-Dev

[Python-Dev] Summary of Python tracker Issues

2012-05-18 Thread Python tracker
ACTIVITY SUMMARY (2012-05-11 - 2012-05-18) Python tracker at http://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open3432 (+14) closed 23196 (+53) total 26628 (+67) Open issues wit

Re: [Python-Dev] cpython: Remove outdated statements about threading and imports.

2012-05-18 Thread Antoine Pitrou
On Fri, 18 May 2012 23:16:09 +1000 Nick Coghlan wrote: > I know you fixed the deadlock problem, but the warnings about shutdown > misbehaviour are still valid. Do we have a reproducer? It should have been fixed by http://bugs.python.org/issue1856. Regards Antoine. ___

Re: [Python-Dev] [Python-checkins] cpython: Remove outdated statements about threading and imports.

2012-05-18 Thread Nick Coghlan
I know you fixed the deadlock problem, but the warnings about shutdown misbehaviour are still valid. -- Sent from my phone, thus the relative brevity :) On May 18, 2012 9:59 PM, "antoine.pitrou" wrote: > http://hg.python.org/cpython/rev/565734c9b66d > changeset: 77020:565734c9b66d > parent:

Re: [Python-Dev] C-level duck typing

2012-05-18 Thread Dag Sverre Seljebotn
On 05/18/2012 12:57 AM, Nick Coghlan wrote: I think the main things we'd be looking for would be: - a clear explanation of why a new metaclass is considered too complex a solution - what the implications are for classes that have nothing to do with the SciPy/NumPy ecosystem - how subclassing woul