Bengt Richter wrote:
> Anyhow, why shouldn't you be able to call freeze(an_ordinary_list) and get
> back freeze(xlist(an_ordinary_list))
> automatically, based e.g. on a freeze_registry_dict[type(an_ordinary_list)]
> => xlist lookup, if plain hash fails?
[Cue: sound of loud alarm bells going of
Smith wrote:
> When teaching some programming to total newbies, a common frustration
> is how to explain why a==b is False when a and b are floats computed
> by different routes which ``should'' give the same results (if
> arithmetic had infinite precision).
This is just a special
Martin v. Löwis wrote:
> then, in C++, 4.4p4 [conv.qual] has a rather longish formula to
> decide that the assignment is well-formed. In essence, it goes
> like this:
>
> [A large head-exploding set of rules]
Blarg.
Const - Just Say No.
Greg
___
Pyt
Neal Norwitz wrote:
> On 2/11/06, Tim Peters <[EMAIL PROTECTED]> wrote:
>
>>>[Tim telling how I broke pyuthon]
>>
>>[Martin fixing it]
>
>
> Sorry for the breakage (I didn't know about the Windows issues).
> Thank you Martin for fixing it. I agree with the solution.
>
> I was away from mail,
Robert wrote:
> Any ideas how to make this work/correct?
Why is that a question for python-dev?
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mai
Eric Sumner <[EMAIL PROTECTED]> wrote:
> Forgive me if someone has already come up with this; I know I am
> coming to the party several months late. All of the proposals for
> decorators (including the accepted one) seemed a bit kludgey to me,
> and I couldn't figure out why. When I read PEP 343
Forgive me if someone has already come up with this; I know I am
coming to the party several months late. All of the proposals for
decorators (including the accepted one) seemed a bit kludgey to me,
and I couldn't figure out why. When I read PEP 343, I realized that
they all provide a solution fo
"Alan Gauld" <[EMAIL PROTECTED]> wrote:
> However I do dislike the name nice() - there is already a nice() in the
> os module with a fairly well understood function. But I'm sure some
> time with a thesaurus can overcome that single mild objection. :-)
Presumably it would be located somewhere lik
I have no particularly strong view on the concept (except that I usually
see the "problem" as a valuable opportunity to introduce a concept
that has far wider reaching consequences than floating point
numbers!).
However I do dislike the name nice() - there is already a nice() in the
os module with
Fwd: news:<[EMAIL PROTECTED]>
After failing on a yield/iterator-continuation problem in Python (see
below) I tried the Ruby (1.8.2) language first time on that construct:
The example tries to convert a block callback interface
(Net::FTP.retrbinary) into a read()-like iterator function in order to
"Phillip J. Eby" <[EMAIL PROTECTED]> writes:
> At 12:21 PM 2/10/2006 -0800, Guido van Rossum wrote:
>> >PEP 343: The "with" Statement
>>
>>Didn't Michael Hudson have a patch?
>
> PEP 343's "Accepted" status was reverted to "Draft" in October, and then
> changed back to "Accepted". I believe
I've been thinking
about a function that was recently proposed at python-dev named 'areclose'.
It is a function that is meant to tell whether two (or possible more) numbers
are close to each other. It is a function similar to one that exists in
Numeric. One such implementation is
def
arec
Neal Norwitz wrote:
> I'm tempted to say we should merge now. I know the branch works on
> 64-bit boxes. I can test on a 32-bit box if Martin hasn't already.
> There will be a lot of churn fixing problems, but maybe we can get
> more people involved.
The ssize_t branch has now all the API I wan
On Sat, Feb 11, 2006 at 10:38:10PM -0800, Neal Norwitz wrote:
> On 2/10/06, Georg Brandl <[EMAIL PROTECTED]> wrote:
> > I am not experienced in releasing, but with the multitude of new things
> > introduced in Python 2.5, could it be a good idea to release an early alpha
> > not long after all (mo
14 matches
Mail list logo
