"Rauli Ruohonen" <[EMAIL PROTECTED]> wrote:
> On 5/27/07, Stephen J. Turnbull <[EMAIL PROTECTED]> wrote:
> >James Y Knight writes:
> >> a 'pyidchar.txt' file with a list of character ranges, and now that
> >> pyidchar.txt file is going to have separate sections based on module
> >> name? Sorry, bu
Greg Ewing schrieb:
> Terry Reedy wrote:
>> It would generate the sequence of partial reductions (potentially
>> indefinately).
>> list(ireduce(summer, 0, range(5)) = [0, 1, 3, 6, 10]
>>
>> This is obviously *not* the same as a reduce() which only returns the final
>> value without the intermedi
Some more thoughts on this, and some questions.
PEP 3101 defines two layers of APIs for string formatting: a low-level
formatting engine, and a high-level set of convenience methods
(primarily str.format).
Both layers have grown complex due to the desire to satisfy feature
requests that have b
Talin wrote:
> Some more thoughts on this, and some questions.
>
> PEP 3101 defines two layers of APIs for string formatting: a low-level
> formatting engine, and a high-level set of convenience methods
> (primarily str.format).
>
> Both layers have grown complex due to the desire to satisfy fe
Eric V. Smith wrote:
> One comment I'd like to make on your prior email is that I'd like to see
> this implemented in 2.6. To my knowledge, we're not removing any
> functionality in 3.0 that will be replaced by str.format, so I can't
> argue that it will make it easier to have code that runs i
On 6/2/07, Josiah Carlson <[EMAIL PROTECTED]> wrote:
> """
> If a comment in the first or second line of the Python script matches
> the regular expression coding[=:]\s*([-\w.]+), this comment is processed
> as an encoding declaration; the first group of this expression names the
> encoding of the
"Rauli Ruohonen" <[EMAIL PROTECTED]> wrote:
> On 6/2/07, Josiah Carlson <[EMAIL PROTECTED]> wrote:
> > """
> > If a comment in the first or second line of the Python script matches
> > the regular expression coding[=:]\s*([-\w.]+), this comment is processed
> > as an encoding declaration; the firs
On 6/2/07, Josiah Carlson <[EMAIL PROTECTED]> wrote:
> Whether or not there exists a tool to convert from Python 2.6 to
> Python 3.0 (2to3), every tool that currently handles Python source
> code encodings via the method specified in the documentation
> (just about every Python-centric editor I kno
> Sincere question: if these characters aren't needed, why are they
> provided? From what I can tell by googling, they're needed when, e.g.,
> Arabic is embedded in an otherwise left-to-right script. Do I have
> that right?
I think not. In principle, each character has a directionality
(available
"Rauli Ruohonen" <[EMAIL PROTECTED]> wrote:
>
> On 6/2/07, Josiah Carlson <[EMAIL PROTECTED]> wrote:
> > Whether or not there exists a tool to convert from Python 2.6 to
> > Python 3.0 (2to3), every tool that currently handles Python source
> > code encodings via the method specified in the docum
On 6/2/07, Stephen J. Turnbull <[EMAIL PROTECTED]> wrote:
> That's not the point; this is like the logical operations on decimal
> thing. Adopting a standard in full is reassuring to potential users,
> who won't complain, they just go away.
...
> We only *need* to do it if we want to claim Unicod
On 6/2/07, Rauli Ruohonen <[EMAIL PROTECTED]> wrote:
> On 6/2/07, Josiah Carlson <[EMAIL PROTECTED]> wrote:
> > Your suggestion would unnecessarily change the semantics of the encoding
> > declarations. I would call this gratuitous breakage.
> Depending on what the regular expression for the dec
12 matches
Mail list logo
