On Mon, Oct 01, 2012 at 11:50:10PM +0200, Christian Heimes
wrote:
> Am 30.09.2012 14:01, schrieb Oleg Broytman:
> >Many kudos to the team and to all contributors!
> >
> >Linux Weekly News regularly publishes tables "Who done what in Linux
> > Kernel": http://lwn.net/Articles/507986/
> >
Am 30.09.2012 14:01, schrieb Oleg Broytman:
>Many kudos to the team and to all contributors!
>
>Linux Weekly News regularly publishes tables "Who done what in Linux
> Kernel": http://lwn.net/Articles/507986/
> http://lwn.net/SubscriberLink/517564/bec11e6ace6ad699/
>
>It would be inter
On 09/29/2012 06:53 PM, Antoine Pitrou wrote:
Hello,
I've created a 3.3 category on the buildbots:
http://buildbot.python.org/3.3/
http://buildbot.python.org/3.3.stable/
Someone will have to update the following HTML page:
http://python.org/dev/buildbot/
Should be done now.
Georg
On Sun, Sep 30, 2012 at 01:26:28PM +0200, Georg Brandl wrote:
> Thanks. It's really a team effort: a little digging in the hg history says
> that:
>
> * 86 people have committed during the 3.3 development
> * 70 during 3.2 development and
> * 55 during 3.1 development
>
> No surprise the feature
Thanks. It's really a team effort: a little digging in the hg history says
that:
* 86 people have committed during the 3.3 development
* 70 during 3.2 development and
* 55 during 3.1 development
No surprise the feature list is so long...
cheers,
Georg
On 09/29/2012 05:52 PM, Guido van Rossum w
Stefan Krah wrote:
> Precision: 19 decimal digits
>
> float:
> result: 3.1415926535897927
> time: 0.112874s
>
> cdecimal:
> result: 3.141592653589793236
> time: 0.348100s
>
> decimal:
> result: 3.141592653589793236
> time: 43.241220s
Apparently there were concerns about the correctness of the
On 9/29/2012 2:38 PM, Guido van Rossum wrote:
Does this mean we want to re-open the discussion about decimal constants?
Last time this came up I think we decided that we wanted to wait for
cdecimal (which is obviously here) and work out how to handle contexts, the
syntax, etc.
I think that oug
On Sat, Sep 29, 2012 at 10:09 PM, R. David Murray wrote:
> On Sun, 30 Sep 2012 08:01:00 +1000, Tim Delaney
> wrote:
>> Also the example at
>> http://docs.python.org/py3k/whatsnew/3.3.html#pep-409-suppressing-exception-contextreads:
>>
>> ... raise AttributeError(attr) from None...
>>
On Sun, 30 Sep 2012 08:01:00 +1000, Tim Delaney
wrote:
> Also the example at
> http://docs.python.org/py3k/whatsnew/3.3.html#pep-409-suppressing-exception-contextreads:
>
> ... raise AttributeError(attr) from None...
>
> Looks like there's an elipsis there that shouldn't be.
This a
On Sep 29, 2012 2:38 PM, "Guido van Rossum" wrote:
>
> On Sat, Sep 29, 2012 at 11:26 AM, Brett Cannon wrote:
> >
> >
> > On Sat, Sep 29, 2012 at 9:07 AM, Paul Moore wrote:
> >>
> >> On 29 September 2012 10:17, Stefan Krah wrote:
> >> > Tim Delaney wrote:
> >> >> If those numbers are similar in
In article
,
Tim Delaney wrote:
> BTW, "What's New": http://www.python.org/download/releases/3.3.0/ still
> says 80x for decimal performance.
Thanks for the report. The page has now been updated to match the final
3.3.0 release announcement post.
--
Ned Deily,
n...@acm.org
__
Also the example at
http://docs.python.org/py3k/whatsnew/3.3.html#pep-409-suppressing-exception-contextreads:
... raise AttributeError(attr) from None...
Looks like there's an elipsis there that shouldn't be.
Tim Delaney
___
Python-Dev mail
BTW, "What's New": http://www.python.org/download/releases/3.3.0/ still
says 80x for decimal performance.
Tim Delaney
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.or
On Sun, Sep 30, 2012 at 4:26 AM, Brett Cannon wrote:
> Does this mean we want to re-open the discussion about decimal constants?
> Last time this came up I think we decided that we wanted to wait for
> cdecimal (which is obviously here) and work out how to handle contexts, the
> syntax, etc.
Just
On Sat, Sep 29, 2012 at 11:26 AM, Brett Cannon wrote:
>
>
> On Sat, Sep 29, 2012 at 9:07 AM, Paul Moore wrote:
>>
>> On 29 September 2012 10:17, Stefan Krah wrote:
>> > Tim Delaney wrote:
>> >> If those numbers are similar in other benchmarks, would it be accurate
>> >> and/or
>> >> reasonable
On Sat, 29 Sep 2012 10:46:37 -0700, Glenn Linderman
wrote:
> On Sat, Sep 29, 2012 at 5:18 AM, Georg Brandl wrote:
> >> In total, almost 500 API items are new or improved in Python 3.3.
> >> For a more extensive list of changes in 3.3.0, see
> >>
> >> http://docs.python.org/3.3/whatsnew/3.3
On Sat, Sep 29, 2012 at 9:07 AM, Paul Moore wrote:
> On 29 September 2012 10:17, Stefan Krah wrote:
> > Tim Delaney wrote:
> >> If those numbers are similar in other benchmarks, would it be accurate
> and/or
> >> reasonable to include a statement along the lines of:
> >>
> >> "comparable to flo
On Sat, Sep 29, 2012 at 5:18 AM, Georg Brandl wrote:
In total, almost 500 API items are new or improved in Python 3.3.
For a more extensive list of changes in 3.3.0, see
http://docs.python.org/3.3/whatsnew/3.3.html
Reading this to see if I missed anything while downloading the new releas
Hello,
I've created a 3.3 category on the buildbots:
http://buildbot.python.org/3.3/
http://buildbot.python.org/3.3.stable/
Someone will have to update the following HTML page:
http://python.org/dev/buildbot/
Regards
Antoine.
On Sat, 29 Sep 2012 14:18:54 +0200
Georg Brandl wrote:
> On beha
> Agreed - this is a really nice release, thanks to all who put it together.
+1
Thank you!
Malcolm
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/
On 09/29/2012 08:23 AM, Amit Saha wrote:
> On Sat, Sep 29, 2012 at 10:18 PM, Georg Brandl wrote:
>>
>>
>> For a more extensive list of changes in 3.3.0, see
>>
>> http://docs.python.org/3.3/whatsnew/3.3.html
> Redirects to http://docs.python.org/py3k/whatsnew/3.3.html: 404 Not Found.
>
>
Wor
Congrats Georg and team! I am incredibly proud of you all for
producing such a great release. As the marketeers would say, "Python
3.3 is the best Python ever!" The feature list is amazing.
--Guido
On Sat, Sep 29, 2012 at 5:18 AM, Georg Brandl wrote:
> On behalf of the Python development team, I
On 29 September 2012 14:24, Eli Bendersky wrote:
> On Sat, Sep 29, 2012 at 5:18 AM, Georg Brandl wrote:
>> On behalf of the Python development team, I'm delighted to announce the
>> Python 3.3.0 final release.
>>
>
> Yay :)
Agreed - this is a really nice release, thanks to all who put it togethe
On Sat, Sep 29, 2012 at 5:18 AM, Georg Brandl wrote:
> On behalf of the Python development team, I'm delighted to announce the
> Python 3.3.0 final release.
>
Yay :)
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listin
On 29 September 2012 10:17, Stefan Krah wrote:
> Tim Delaney wrote:
>> If those numbers are similar in other benchmarks, would it be accurate and/or
>> reasonable to include a statement along the lines of:
>>
>> "comparable to float performance - usually no more than 3x for calculations
>> within
On Sat, Sep 29, 2012 at 10:37 PM, Dave Angel wrote:
> On 09/29/2012 08:23 AM, Amit Saha wrote:
>> On Sat, Sep 29, 2012 at 10:18 PM, Georg Brandl wrote:
>>>
>>>
>>> For a more extensive list of changes in 3.3.0, see
>>>
>>> http://docs.python.org/3.3/whatsnew/3.3.html
>> Redirects to http://
On Sat, Sep 29, 2012 at 10:18 PM, Georg Brandl wrote:
> On behalf of the Python development team, I'm delighted to announce the
> Python 3.3.0 final release.
>
> Python 3.3 includes a range of improvements of the 3.x series, as well
> as easier porting between 2.x and 3.x. Major new features and
On behalf of the Python development team, I'm delighted to announce the
Python 3.3.0 final release.
Python 3.3 includes a range of improvements of the 3.x series, as well
as easier porting between 2.x and 3.x. Major new features and changes
in the 3.3 release series are:
* PEP 380, syntax for d
Antoine Pitrou wrote:
> > Wow! I had no idea cdecimal was that close in speed to float. That's
> > seriously impressive.
>
> I think this means the performance difference is on the same order
> of magnitude as the CPython interpretation overhead. Still, it's
> impressive indeed.
Of course, if yo
Tim Delaney wrote:
> If those numbers are similar in other benchmarks, would it be accurate and/or
> reasonable to include a statement along the lines of:
>
> "comparable to float performance - usually no more than 3x for calculations
> within the range of numbers covered by float"
For numerical
On Fri, 28 Sep 2012 21:51:39 +0100
Paul Moore wrote:
> On 28 September 2012 19:19, Stefan Krah wrote:
> > Brett Cannon wrote:
> >> Georg Brandl wrote:
> >> > * A C implementation of the "decimal" module, with up to 80x speedup
> >> > for decimal-heavy applications
> >>
> >>
On 29 September 2012 07:50, Tim Delaney wrote:
> On 29 September 2012 06:51, Paul Moore wrote:
>
>>
>> Wow! I had no idea cdecimal was that close in speed to float. That's
>> seriously impressive.
>>
>
> If those numbers are similar in other benchmarks, would it be accurate
> and/or reasonable t
On 29 September 2012 06:51, Paul Moore wrote:
>
> Wow! I had no idea cdecimal was that close in speed to float. That's
> seriously impressive.
>
If those numbers are similar in other benchmarks, would it be accurate
and/or reasonable to include a statement along the lines of:
"comparable to flo
On 28 September 2012 19:19, Stefan Krah wrote:
> Brett Cannon wrote:
>> Georg Brandl wrote:
>> > * A C implementation of the "decimal" module, with up to 80x speedup
>> > for decimal-heavy applications
>>
>> Could you bump up the factor to 120x in the final announcement? Ther
Brett Cannon wrote:
> Georg Brandl wrote:
> > * A C implementation of the "decimal" module, with up to 80x speedup
> > for decimal-heavy applications
>
> Could you bump up the factor to 120x in the final announcement? There were
> a couple of performance improvements in t
On Fri, Sep 28, 2012 at 11:40 AM, Stefan Krah wrote:
> Georg Brandl wrote:
> > * A C implementation of the "decimal" module, with up to 80x speedup
> > for decimal-heavy applications
>
> Could you bump up the factor to 120x in the final announcement? There were
> a couple of performance impr
Georg Brandl wrote:
> * A C implementation of the "decimal" module, with up to 80x speedup
> for decimal-heavy applications
Could you bump up the factor to 120x in the final announcement? There were
a couple of performance improvements in the meantime, and this is what I'm
consistently measur
Mark Lawrence wrote:
On 24/09/2012 07:18, Georg Brandl wrote:
[snip impressive list of improvements]
Yes, but apart from all that, what have the python devs ever done for
us? Nothing :)
I'll take that kind of nothing any day of the week! ;)
~Ethan~
__
On 24/09/2012 07:18, Georg Brandl wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On behalf of the Python development team, I'm delighted to announce the
third release candidate of Python 3.3.0.
This is a preview release, and its use is not recommended in
production settings.
Python 3.3 i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On behalf of the Python development team, I'm delighted to announce the
third release candidate of Python 3.3.0.
This is a preview release, and its use is not recommended in
production settings.
Python 3.3 includes a range of improvements of the 3.x
Indeed, thanks for catching that.
The GPG signatures are good, so the downloads are the original ones
built by Martin.
Georg
On 11.09.2012 18:11, Perica Zivkovic wrote:
> Just a small note, MD5 for RC2 file python-3.3.0rc2.msi is not correct on
> http://python.org/download/releases/3.3.0/
>
>
Just a small note, MD5 for RC2 file python-3.3.0rc2.msi is not correct on
http://python.org/download/releases/3.3.0/
it would be nice if someone can update it
cheers,
Perica
On Sunday, September 9, 2012 4:25:39 AM UTC-5, Georg Brandl wrote:
> -BEGIN PGP SIGNED MESSAGE-
>
> Hash: SHA1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On behalf of the Python development team, I'm delighted to announce the
second release candidate of Python 3.3.0.
This is a preview release, and its use is not recommended in
production settings.
Python 3.3 includes a range of improvements of the 3.x
On behalf of the Python development team, I'm delighted to announce the
first release candidate of Python 3.3.0.
This is a preview release, and its use is not recommended in
production settings.
Python 3.3 includes a range of improvements of the 3.x series, as well
as easier porting between 2.x
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On behalf of the Python development team, I'm happy to announce the
second beta release of Python 3.3.0 -- a little later than originally
scheduled, but much better for it.
This is a preview release, and its use is not recommended in
production settin
All,
Congradulations. This is a big one!
On Wed, Jun 27, 2012 at 2:10 AM, Georg Brandl wrote:
> On behalf of the Python development team, I'm happy to announce the
> first beta release of Python 3.3.0.
>
> This is a preview release, and its use is not recommended in
> production settings.
>
>
On 06/26/2012 11:10 PM, Georg Brandl wrote:
On behalf of the Python development team, I'm happy to announce the
first beta release of Python 3.3.0.
I <3 <3.<3
Thanks Georg! And everybody who contributed.
Stoked,
//arry/
___
Python-Dev mailing lis
On behalf of the Python development team, I'm happy to announce the
first beta release of Python 3.3.0.
This is a preview release, and its use is not recommended in
production settings.
Python 3.3 includes a range of improvements of the 3.x series, as well
as easier porting between 2.x and 3.x.
On behalf of the Python development team, I'm happy to announce the
fourth alpha release of Python 3.3.0.
This is a preview release, and its use is not recommended in
production settings.
Python 3.3 includes a range of improvements of the 3.x series, as well
as easier porting between 2.x and 3.x.
On 05/07/2012 11:00 AM, Mark Shannon wrote:
> Martin v. Löwis wrote:
>>> The What's New document also starts with a long list of PEPs.
>>> This seems to be the standard format as What's New for 3.2 follows the
>>> same layout.
>>>
>>> Perhaps adding an overview or highlights at the start would be a
Any such summary prose will be written by the What's New author
(Raymond Hettinger for the 3.x series). Such text definitely *won't*
be written until after feature freeze (which occurs with the first
beta, currently planned for late June).
Until that time, the draft What's New is primarily rough n
Martin v. Löwis wrote:
The What's New document also starts with a long list of PEPs.
This seems to be the standard format as What's New for 3.2 follows the
same layout.
Perhaps adding an overview or highlights at the start would be a good
idea.
You seem to assume that Python users are not able
The What's New document also starts with a long list of PEPs.
This seems to be the standard format as What's New for 3.2 follows the
same layout.
Perhaps adding an overview or highlights at the start would be a good
idea.
You seem to assume that Python users are not able to grasp long itemized
Nick Coghlan wrote:
On Wed, May 2, 2012 at 7:55 PM, Mark Shannon wrote:
Or maybe three parts?
New features.
Behavioural changes (i.e. bug fixes)
Performance enhancements
The release PEPs are mainly there for *our* benefit, not end users.
For end users, it's the What's New document that matte
On Wed, May 2, 2012 at 7:55 PM, Mark Shannon wrote:
> Or maybe three parts?
> New features.
> Behavioural changes (i.e. bug fixes)
> Performance enhancements
The release PEPs are mainly there for *our* benefit, not end users.
For end users, it's the What's New document that matters. For
performa
Georg Brandl wrote:
On behalf of the Python development team, I'm happy to announce the
third alpha release of Python 3.3.0.
This is a preview release, and its use is not recommended in
production settings.
Python 3.3 includes a range of improvements of the 3.x series, as well
as easier porting
On behalf of the Python development team, I'm happy to announce the
third alpha release of Python 3.3.0.
This is a preview release, and its use is not recommended in
production settings.
Python 3.3 includes a range of improvements of the 3.x series, as well
as easier porting between 2.x and 3.x.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- -BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On behalf of the Python development team, I'm happy to announce the
second alpha release of Python 3.3.0.
This is a preview release, and its use is not recommended in
production settings.
Python 3.3 in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On behalf of the Python development team, I'm happy to announce the
second alpha release of Python 3.3.0.
This is a preview release, and its use is not recommended in
production settings.
Python 3.3 includes a range of improvements of the 3.x series,
Le 06/03/2012 15:31, Giampaolo Rodolà a écrit :
> That's why I once proposed to include whatsnew.rst changes every time
> a new feature is added/committed.
> Assigning that effort to the release manager or whoever is supposed to
> take care of this, is both impractical and prone to forgetfulness.
On 07.03.2012 08:08, Stefan Behnel wrote:
Jim J. Jewett, 06.03.2012 20:43:
Hash Randomization (issue 13703) is now on by default. Unfortunately,
this does break some tests; it can be temporarily turned off by setting
the environment variable PYTHONHASHSEED to "0" before launching python.
I
Jim J. Jewett, 06.03.2012 20:43:
> Hash Randomization (issue 13703) is now on by default. Unfortunately,
> this does break some tests; it can be temporarily turned off by setting
> the environment variable PYTHONHASHSEED to "0" before launching python.
I don't think that makes it clear enough tha
Il 06 marzo 2012 20:43, Jim J. Jewett ha scritto:
>
>
> In http://mail.python.org/pipermail/python-dev/2012-March/117348.html
> Georg Brandl posted:
>
>> Python 3.3 includes a range of improvements of the 3.x series, as well as
>> easier
>> porting between 2.x and 3.x. Major new features in th
In http://mail.python.org/pipermail/python-dev/2012-March/117348.html
Georg Brandl posted:
> Python 3.3 includes a range of improvements of the 3.x series, as well as
> easier
> porting between 2.x and 3.x. Major new features in the 3.3 release series
> are:
As much as it is nice to just c
On 05.03.2012 14:27, Ned Batchelder wrote:
For a more extensive list of changes in 3.3.0, see
http://docs.python.org/3.3/whatsnew/3.3.html
The 3.3 whatsnews page doesn't seem to mention PEP 414 or Unicode
literals at all.
Indeed. Thanks to Nick, this is now fixed.
Georg
___
On 3/5/2012 2:54 AM, Georg Brandl wrote:
On behalf of the Python development team, I'm happy to announce the
first alpha release of Python 3.3.0.
This is a preview release, and its use is not recommended in
production settings.
Python 3.3 includes a range of improvements of the 3.x series, as w
On behalf of the Python development team, I'm happy to announce the
first alpha release of Python 3.3.0.
This is a preview release, and its use is not recommended in
production settings.
Python 3.3 includes a range of improvements of the 3.x series, as well as easier
porting between 2.x and 3.x.
67 matches
Mail list logo
