On 9/28/07, Brett Cannon <[EMAIL PROTECTED]> wrote:
> On 9/28/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> > On 9/28/07, Stephen J. Turnbull <[EMAIL PROTECTED]> wrote:
> > > Greg Ewing writes:
> > > > Gregory P. Smith wrote:
> > > > > Is IOError is the right name to use? OSError is raised f
"Bruce Frederiksen" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
A 64K attachment. Please do not do such a worse-than-useless thing again.
Especially when only 1K is original.
___
Python-Dev mailing list
Python-Dev@python.org
http://
On 9/28/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On 9/28/07, Stephen J. Turnbull <[EMAIL PROTECTED]> wrote:
> > Greg Ewing writes:
> > > Gregory P. Smith wrote:
> > > > Is IOError is the right name to use? OSError is raised for things that
> > > > are not IO such as subprocess, dlopen,
On Fri, 28 Sep 2007, Raymond Hettinger wrote:
> > Interestingly, they seem to all have something to do with dictionary
> > values() that are themselves iterable.
>
> I see. These are instances of a recurring general use case of
> chain() as a one-level flattener.
>
> Will give consideration t
[Bruce Frederiksen]
I've added a new function to itertools called 'concat'. This
function is
much like chain, but takes all of the iterables as a single
argument.
[Raymond]
>> Any practical use cases or is this just a theoretical improvement?
>>
>> For Py2.x, I'm not wil
On 28-Sep-07, at 10:45 AM, Raymond Hettinger wrote:
> [Bruce Frederiksen]
>>> I've added a new function to itertools called 'concat'. This
>>> function is
>>> much like chain, but takes all of the iterables as a single
>>> argument.
>
> Any practical use cases or is this just a theoretical i
> I'm trying to build Python (2.6) with GCC the option -Wwrite-strings.
>
> 1 - Is there any interest on this?
It might be nice to have, but will certainly come at a cost. So feel
free to try this out; at the end, we might agree that this change is
too intrusive.
> 2 - What should I do for the v
On 9/28/07, Stephen J. Turnbull <[EMAIL PROTECTED]> wrote:
> Greg Ewing writes:
> > Gregory P. Smith wrote:
> > > Is IOError is the right name to use? OSError is raised for things that
> > > are not IO such as subprocess, dlopen, system.
> >
> > The trouble with either of these is that the cl
Greg Ewing writes:
> Gregory P. Smith wrote:
> > Is IOError is the right name to use? OSError is raised for things that
> > are not IO such as subprocess, dlopen, system.
>
> The trouble with either of these is that the class
> of errors we're talking about don't necessarily come
> direct
On 26/09/2007, Dino Viehland <[EMAIL PROTECTED]> wrote:
> My understanding is that users can write code that uses only \n and Python
> will write the
> end-of-line character(s) that are appropriate for the platform when writing
> to a file. That's
> what I meant by uses \n for everything interna
[Bruce Frederiksen]
>> I've added a new function to itertools called 'concat'. This function is
>> much like chain, but takes all of the iterables as a single argument.
Any practical use cases or is this just a theoretical improvement?
For Py2.x, I'm not willing to unnecessarily expand the modu
ACTIVITY SUMMARY (09/21/07 - 09/28/07)
Tracker at http://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue
number. Do NOT respond to this message.
1278 open (+16) / 11424 closed (+17) / 12702 total (+33)
Open issues with patches: 415
Average durati
On 9/22/07, Bruce Frederiksen <[EMAIL PROTECTED]> wrote:
>
> I've added a new function to itertools called 'concat'. This function is
> much like chain, but takes all of the iterables as a single argument. Thus
> concat(some_iterables) is logically equivalent to chain(*some_iterables);
> the dif
On 9/22/07, Bruce Frederiksen <[EMAIL PROTECTED]> wrote:
>
> I've added a new function to itertools called 'concat'. This function is
> much like *chain*, but takes all of the iterables as a single argument.
>
I've needed this once or twice, though my implementation was called
'starchain', in li
[EMAIL PROTECTED] schrieb:
> I'd like to help out cleaning up the Python3.0 documentation. There are a
> lot of little leftovers from 2.x that are no longer true. (mentions of
> long, callable() etc.)
I've applied the first four patches, thank you!
Georg
--
Thus spake the Lord: Thou shalt ind
Thomas Wouters schrieb:
> On 9/27/07, Eric Smith <[EMAIL PROTECTED]> wrote:
>>
>> Thomas Wouters wrote:
>>
>> > Unfortunately, that's not how it works :-) If you check something into
>> > the trunk, it will be merged into Py3k sooner or later. I may ask the
>> > original submitter for assistance if
16 matches
Mail list logo
