Martin v. Löwis wrote:
> Guido van Rossum schrieb:
>> Are you interested in doing this at the Google sprint next week?
>
> Sure; I hadn't any special plans so far.
>
>> What do you think?
>
> Sounds good. There are two problems I see:
>
> - how to benchmark?
>
> - there are subtle details in t
Nick Coghlan <[EMAIL PROTECTED]> writes:
> PyInt_AsLong can already fail with OverflowError
> it accepts arbitrary objects and coerces them to integers via
> __int__, instead of just accepting PyInt instances.
If it calls __int__, it can fail with any exception resulting from
user code.
Greppin
Alexander Belopolsky wrote:
> The new API does not seem to provide for a way to read
> data directly into an existing object without creating
> an intermediate bytes object.
This is among the several things that Itamar Shtull-Trauring mentioned
during his PyCon 2005 talk on 'Fast Networking with P
python.org Webmaster wrote:
> Dear Wiki user,
>
> You have subscribed to a wiki page or wiki category on "PythonInfo Wiki" for
> change notification.
>
> The following page has been changed by 65.57.245.11:
> http://wiki.python.org/moin/GoogleSprintPy3k
>
> -
On 8/21/06, Georg Brandl <[EMAIL PROTECTED]> wrote:
> python.org Webmaster wrote:
> > - * Make zip() an iterator (like itertools.zip())
> > + * Make zip() an iterator (like itertools.izip())
> > +
> > + * Make map() and filter() iterators and make them stop at the end of the
> > shortest input
On 8/21/06, Georg Brandl <[EMAIL PROTECTED]> wrote:
> > + * Make map() and filter() iterators and make them stop at the end of the
> > shortest input (like zip()) instead of at the end of the longest input
>
> May I suggest an additional keyword(-only?) argument to get the old behavior,
> stoppin
On 8/21/06, Collin Winter <[EMAIL PROTECTED]> wrote:
> I thought map() and filter() were going away in Py3k? Did that change?
I still find them useful when using a built-in function, and unlike
reduce(), I have no trouble reading and understanding such code.
--
--Guido van Rossum (home page: htt
On 8/21/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On 8/21/06, Collin Winter <[EMAIL PROTECTED]> wrote:
> > I thought map() and filter() were going away in Py3k? Did that change?
>
> I still find them useful when using a built-in function, and unlike
> reduce(), I have no trouble reading and
On 8/21/06, Collin Winter <[EMAIL PROTECTED]> wrote:
> On 8/21/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> > On 8/21/06, Collin Winter <[EMAIL PROTECTED]> wrote:
> > > I thought map() and filter() were going away in Py3k? Did that change?
> >
> > I still find them useful when using a built-in
On 8/21/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> Perhaps there could be (or is there already?) a helper in itertools
> that iterates over multiple iterables padding the shorter inputs with
> None to the length of the longest one.
I think the most convenient solution would be to handle thi
On 8/21/06, Fredrik Johansson <[EMAIL PROTECTED]> wrote:
> On 8/21/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> > Perhaps there could be (or is there already?) a helper in itertools
> > that iterates over multiple iterables padding the shorter inputs with
> > None to the length of the longest
Zitat von Alexander Belopolsky <[EMAIL PROTECTED]>:
> > Alexander Belopolsky schrieb:
> >> For Py3k, I would like to suggest a buffer protocol modelled
> >> after iovec structure that is used by the readv system call.
> >
> > -1
>
> What is this -1 for:
>
> a) buffer protocol in Py3k?
> b) multise
On 8/21/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On 8/21/06, Fredrik Johansson <[EMAIL PROTECTED]> wrote:
> > On 8/21/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> > > Perhaps there could be (or is there already?) a helper in itertools
> > > that iterates over multiple iterables paddin
On 8/21/06, Fredrik Johansson <[EMAIL PROTECTED]> wrote:
> On 8/21/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> > On 8/21/06, Fredrik Johansson <[EMAIL PROTECTED]> wrote:
> > > On 8/21/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> > > > Perhaps there could be (or is there already?) a helpe
Talin <[EMAIL PROTECTED]> wrote:
[snip]
> I've been thinking about the transition to unicode strings, and I want
> to put forward a notion that might allow the transition to be done
> gradually instead of all at once.
>
> The idea would be to temporarily introduce a new name for 8-bit strings
On Mon, 21 Aug 2006 14:21:30 -0700, Josiah Carlson <[EMAIL PROTECTED]> wrote:
>
>Talin <[EMAIL PROTECTED]> wrote:
>[snip]
>> I've been thinking about the transition to unicode strings, and I want
>> to put forward a notion that might allow the transition to be done
>> gradually instead of all at on
On 8/21/06, Josiah Carlson <[EMAIL PROTECTED]> wrote:
> As we approach Py3k, I again ask, "what are the compelling features?"
> Wholesale breakage of anything that uses ascii strings as text or binary
> data? A completely changed IO stack (requiring re-learning of everything
> known about Python IO
On 8/21/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> I'd like map(f, a, b) to be the same as to (f(*x) for x in zip(a, b))
> so we have to explain less. (And I think even map(f, *args) === (f(*x)
> for x in zip(*args)).)
Should map(None, a, b) == zip(a, b), leaving python with multiple ways
t
On 8/21/06, Michael Urman <[EMAIL PROTECTED]> wrote:
> On 8/21/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> > I'd like map(f, a, b) to be the same as to (f(*x) for x in zip(a, b))
> > so we have to explain less. (And I think even map(f, *args) === (f(*x)
> > for x in zip(*args)).)
>
> Should m
"Guido van Rossum" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> On 8/21/06, Josiah Carlson <[EMAIL PROTECTED]> wrote:
>> When
>> everyone has to rewrite their code, they are going to ask, "Why don't I
>> just stick with the maintenance 2.x? It's going to be maintained for a
>>
On 8/21/06, Collin Winter <[EMAIL PROTECTED]> wrote:
> On 8/21/06, Michael Urman <[EMAIL PROTECTED]> wrote:
> > On 8/21/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> > > I'd like map(f, a, b) to be the same as to (f(*x) for x in zip(a, b))
> > > so we have to explain less. (And I think even map
21 matches
Mail list logo
