Re: [Python-Dev] [RELEASE] Python 2.7.4 release candidate 1
Any plans backport decimal C implementation from 3.3? Thanks. Andriy Kornatskyy > Date: Tue, 26 Mar 2013 16:18:34 -0700 > From: ether@gmail.com > To: h...@ox.cx > CC: python-dev@python.org > Subject: Re: [Python-Dev] [RELEASE] Python 2.7.4 release candidate 1 > > On Tue, Mar 26, 2013 at 3:26 PM, Hynek Schlawack wrote: > > Speakerdeck is slides only. The video is here: > > http://pyvideo.org/video/1730/python-33-trust-me-its-better-than-27 > > Sweet thanks! > ___ > 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/andriy.kornatskyy%40live.com > ___ 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
Re: [Python-Dev] [RELEASE] Python 2.7.4 release candidate 1
Andrew, Thank you for the prompt response back. > will never be backported. Who knows? Is python 3.3 _decimal interface 100% compatible with one pure python implementation in 2.7? I suppose code written using decimals in python 2.7 should work in python 3 with no changes, or there should be taken caution for something? According to presentation slides, 30x performance boost is something definitely valuable for 2.7 crowd. Thanks. Andriy > Date: Wed, 27 Mar 2013 10:24:47 +0200 > Subject: Re: [Python-Dev] [RELEASE] Python 2.7.4 release candidate 1 > From: andrew.svet...@gmail.com > To: andriy.kornats...@live.com > CC: python-dev@python.org > > No. _decimal is new functionality that will never be backported. > > On Wed, Mar 27, 2013 at 9:40 AM, Andriy Kornatskyy > wrote: > > Any plans backport decimal C implementation from 3.3? > > > > Thanks. > > > > Andriy Kornatskyy > > > > > > > >> Date: Tue, 26 Mar 2013 16:18:34 -0700 > >> From: ether@gmail.com > >> To: h...@ox.cx > >> CC: python-dev@python.org > >> Subject: Re: [Python-Dev] [RELEASE] Python 2.7.4 release candidate 1 > >> > >> On Tue, Mar 26, 2013 at 3:26 PM, Hynek Schlawack wrote: > >> > Speakerdeck is slides only. The video is here: > >> > http://pyvideo.org/video/1730/python-33-trust-me-its-better-than-27 > >> > >> Sweet thanks! > >> ___ > >> 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/andriy.kornatskyy%40live.com > > ___ > > 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/andrew.svetlov%40gmail.com > > > > -- > Thanks, > Andrew Svetlov ___ 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
Re: [Python-Dev] [RELEASE] Python 2.7.4 release candidate 1
> No. 2.7 does not accept new features anymore, It is clear now. > but you can install this backport from PyPI: > https://pypi.python.org/pypi/cdecimal/2.3 This is what I was looking for. Thanks. Andriy > Date: Wed, 27 Mar 2013 10:54:37 +0100 > Subject: Re: [Python-Dev] [RELEASE] Python 2.7.4 release candidate 1 > From: amaur...@gmail.com > To: andrew.svet...@gmail.com > CC: andriy.kornats...@live.com; python-dev@python.org > > 2013/3/27 Andrew Svetlov > mailto:andrew.svet...@gmail.com>> > No. _decimal is new functionality that will never be backported. > > On Wed, Mar 27, 2013 at 9:40 AM, Andriy Kornatskyy > mailto:andriy.kornats...@live.com>> wrote: > > Any plans backport decimal C implementation from 3.3? > > No. 2.7 does not accept new features anymore, but you can install > this backport from PyPI: https://pypi.python.org/pypi/cdecimal/2.3 > > -- > Amaury Forgeot d'Arc ___ 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
Re: [Python-Dev] PEP 8 and function names
PEP8 consistency is a question to the development team commitment. Nothing prevents you add pep8 checks to build process, contribute fixes. This inconsistency has been analyzed for various web frameworks recently: http://mindref.blogspot.com/2012/10/python-web-pep8-consistency.html No much in the list are paying attention to this... Andriy > Date: Sun, 26 May 2013 11:48:50 +0200 > From: se8@gmail.com > To: python-dev@python.org > Subject: [Python-Dev] PEP 8 and function names > > Hi all, > > "There should be one-- and preferably only one --obvious way to do it." > > We all love this mantra. > > But one thing that often confuses people : function naming. The > standard library is kind of inconsistent. Some functions are separated > by underscores and others aren't. It's not intuitive and new > pythonistas end up constantly reading the doc. (Time saving one char > typing vs time guessing function names.) > > Would it be a good idea to clarify PEP 8 on this ? I mean for future > libraries. > > Regards, > > Sébastien > ___ 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
