[Python-Dev] PEP 429, Release Schedule for Python 3.4, posted
It's essentially identical to the draft I posted last week--nothing new there. Looking forward to February 2014! And, to quote Barry Warsaw, let the wild rumpus begin!, //arry/ ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] PEP 429, Release Schedule for Python 3.4, posted
Should have posted a link, sorry. Here you go: http://www.python.org/dev/peps/pep-0429/ //arry/ On 10/17/2012 04:12 PM, Larry Hastings wrote: It's essentially identical to the draft I posted last week--nothing new there. Looking forward to February 2014! And, to quote Barry Warsaw, let the wild rumpus begin!, //arry/ ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] cpython (3.3): Tweak the threaded example in concurrent.futures
> + url = future_to_url[url] url = future_to_url[future] ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] cpython (3.3): Tweak the threaded example in concurrent.futures
On 16.10.12 15:58, Antoine Pitrou wrote: Adding an "url" attribute here looks a bit ugly to me. Why not use a dict comprehension for future_to_url? This is especially ugly after implementing PEP 412 (Key-Sharing Dictionary). ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] cpython (3.3): Tweak the threaded example in concurrent.futures
Good note! On Wed, Oct 17, 2012 at 7:55 PM, Serhiy Storchaka wrote: > On 16.10.12 15:58, Antoine Pitrou wrote: >> >> Adding an "url" attribute here looks a bit ugly to me. Why not use a >> dict comprehension for future_to_url? > > > This is especially ugly after implementing PEP 412 (Key-Sharing Dictionary). > > > > ___ > Python-Dev mailing list > [email protected] > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > http://mail.python.org/mailman/options/python-dev/andrew.svetlov%40gmail.com -- Thanks, Andrew Svetlov ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Bumping autoconf from 2.68 to 2.69
On 16.10.2012 17:58, David Malcolm wrote: > On Tue, 2012-10-16 at 10:59 +0200, Stefan Krah wrote: >> Charles-François Natali wrote: >>> Well, so I guess all committers will have to use the same >>> Linux/FreeBSD/whatever distribution then? >>> AFAICT there's no requirement regarding the mercurial version used by >>> committers either. >> >> It should be sufficient to install autoconf-x.y into /home/user/bin or >> something similar. Installing autoconf from source really takes about >> 3 minutes. > FWIW this was also documented in the devguide, as of: > http://hg.python.org/devguide/rev/5432be4d4e1a > > though that description was then removed in: > http://hg.python.org/devguide/rev/27be97280cf so maybe this could be restored. the python configure.ac doesn't use that internal and specific autoconf features, so it might be ok to live with the diffs. I didn't see any issues using the system supplied autoconf with any python version on not that recent distro releases. However the effort to use a specific autoconf version for each branch should be minimal (other projects do require this). Matthias ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
