Guido van Rossum wrote:
> On 5/6/06, Talin <[EMAIL PROTECTED]> wrote:
>
>> I've updated PEP 3101 based on the feedback collected so far.
>
> [http://www.python.org/dev/peps/pep-3101/]
>
> I think this is a step in the right direction.
Cool, and thanks for the very detailed feedback.
> I wonder
neal.norwitz wrote:
Please note that the "Need for Speed" sprint runs May 21 - 27.
Bringing the schedule forward on Alpha 3 makes it less possible to
incorporate sprint changes into the 2.5 trunk.
Will it be acceptable to add new (performance) changes between Alpha 3
and beta 1, or would devel
On 5/19/06, Talin <[EMAIL PROTECTED]> wrote:
> Guido van Rossum wrote:
> > [http://www.python.org/dev/peps/pep-3101/]
> > http://msdn.microsoft.com/library/en-us/cpguide/html/cpconcompositeformatting.asp
[on width spec a la .NET]
> We already have that now, don't we? If you look at the docs for "S
On Thu, May 18, 2006, Neal Norwitz wrote:
>
> I moved up the 2.5 release date by a bit. Ideally, I wanted to have
> the final on July 27 which corresponds to OSCON. This seems too
> aggressive since I haven't updated the schedule publicly. So the new
> schedule has rc1 slated for July 27.
>
>
Aahz wrote:
>On Thu, May 18, 2006, Neal Norwitz wrote:
>
>
>>I moved up the 2.5 release date by a bit. Ideally, I wanted to have
>>the final on July 27 which corresponds to OSCON. This seems too
>>aggressive since I haven't updated the schedule publicly. So the new
>>schedule has rc1 slated f
Guido van Rossum wrote:
> [on escaping]
>
>> There is another solution to this which is equally subtle, although
>> fairly straightforward to parse. It involves defining the rules for
>> escapes as follows:
>>
>> '{{' is an escaped '{'
>> '}}' is an escaped '}', unless we are within a fiel
On 5/19/06, Talin <[EMAIL PROTECTED]> wrote:
> Since you seem to be in a PEP-review mode, could you have a look at
> 3102? In particular, it seems that all of the controversies on that one
> have quieted down; Virtually everyone seems in favor of the first part,
> and you have already ruled in favo
I'm having trouble getting the zlib module to build (SVN HEAD). The error is:
building 'zlib' extension
gcc -pthread -fPIC -fno-strict-aliasing -DNDEBUG -g -O3 -Wall
-Wstrict-prototypes -I. -I/home/guido/projects/python/trunk/./Include
-I../Include -I. -I/usr/local/include
-I/home/guido/projects/p
[elventear]
> I am the in the need to do some numerical calculations that involve
> real numbers that are larger than what the native float can handle.
>
> I've tried to use Decimal, but I've found one main obstacle that I
> don't know how to sort. I need to do exponentiation with real
> exponents,
[Guido]
> I'm having trouble getting the zlib module to build (SVN HEAD). The error is:
>
> building 'zlib' extension
> gcc -pthread -fPIC -fno-strict-aliasing -DNDEBUG -g -O3 -Wall
> -Wstrict-prototypes -I. -I/home/guido/projects/python/trunk/./Include
> -I../Include -I. -I/usr/local/include
> -I/
Neal Norwitz wrote:
> I moved up the 2.5 release date by a bit. Ideally, I wanted to have
> the final on July 27 which corresponds to OSCON. This seems too
> aggressive since I haven't updated the schedule publicly. So the new
> schedule has rc1 slated for July 27.
>
> http://www.python.org
Patch / Bug Summary
___
Patches : 378 open ( +0) / 3238 closed (+22) / 3616 total (+22)
Bugs: 907 open (+13) / 5831 closed (+20) / 6738 total (+33)
RFE : 218 open ( +2) / 217 closed ( +2) / 435 total ( +4)
New / Reopened Patches
__
Patch fix
Remember, the feature freeze isn't until beta1. New stuff can still go
in after the next alpha, before beta1.
And pure speedup related items aren't likely to cause feature changes
(I hope)
Anthony
___
Python-Dev mailing list
Python-Dev@python.org
http
On Saturday 20 May 2006 08:23, Andrew MacIntyre wrote:
> I'm sorry, but I find such advancing schedules with little warning
> quite objectionable. Particularly the cutoff for new functionality
> implicit in the last of the alphas.
Nonono. Feature freeze is beta1.
Anthony
--
Anthony Baxter <
Tim Peters wrote:
> That's very peculiar. Python has its own copy of the zlib code now,
> under Modules/zlib/. That's version 1.2.3.
>
> http://mail.python.org/pipermail/python-dev/2005-December/058873.html
>
> inflateCopy() is exported by Modules/zlib/inflate.c. I wonder why the
> last gc
Guido van Rossum wrote:
> It seems I have libz 1.1.4. Is this no longer supported?
Apparently so. This function started to be used with
r46012 | georg.brandl | 2006-05-16 09:38:27 +0200 (Di, 16 Mai 2006) | 3
lines
Geänderte
16 matches
Mail list logo
