On Sun, 01 Oct 2006 13:56:53 +1000, Nick Coghlan <[EMAIL PROTECTED]> wrote:
>Things the PEP 355 path object lumps together:
> - string manipulation operations
> - abstract path manipulation operations (work for non-existent filesystems)
> - read-only traversal of a concrete filesystem (dir
Hans Polak wrote:
> Hi,
>
>
>
> Just an opinion, but many uses of the ‘while true loop’ are instances of
> a ‘do loop’. I appreciate the language layout question, so I’ll give you
> an alternative:
>
>
>
> do:
>
>
>
>
>
> while
>
I believe you m
Giovanni Bajo wrote:
> Guido van Rossum wrote:
>
>> OK. Pronouncement: PEP 355 is dead. The authors (or the PEP editor)
>> can update the PEP.
>>
>> I'm looking forward to a new PEP.
>
> It would be terrific if you gave us some clue about what is wrong in PEP355,
> so
> that the next guy does no
Patch / Bug Summary
___
Patches : 422 open ( +2) / 3415 closed ( +5) / 3837 total ( +7)
Bugs: 933 open (+18) / 6212 closed (+26) / 7145 total (+44)
RFE : 237 open ( +2) / 239 closed ( +1) / 476 total ( +3)
New / Reopened Patches
__
platform.
On 9/30/06, Scott David Daniels <[EMAIL PROTECTED]> wrote:
> Bob Ippolito wrote:
> > On 9/30/06, Scott David Daniels <[EMAIL PROTECTED]> wrote:
> >> Christos Georgiou wrote:
> >>> Does anyone know why this happens? I can't find any information pointing
> >>> to
> >>> this being deliberate.
> >> Al
Bob Ippolito wrote:
> On 9/30/06, Scott David Daniels <[EMAIL PROTECTED]> wrote:
>> Christos Georgiou wrote:
>>> Does anyone know why this happens? I can't find any information pointing to
>>> this being deliberate.
>> Also note: the Os/X universal seems to include a Tix runtime for the
>>
On 9/30/06, Scott David Daniels <[EMAIL PROTECTED]> wrote:
> Christos Georgiou wrote:
> > Does anyone know why this happens? I can't find any information pointing to
> > this being deliberate.
> >
> > I just upgraded to 2.5 on Windows (after making sure I can build extensions
> > with the freeware
Steve> By these statistics I think the answer to the original question
Steve> is clearly "no" in the general case.
As someone else (Guido?) pointed out, the literal case isn't all that
interesting. I modified floatobject.c to track a few interesting
floating point values:
static uns
Guido van Rossum wrote:
> OK. Pronouncement: PEP 355 is dead. The authors (or the PEP editor)
> can update the PEP.
>
> I'm looking forward to a new PEP.
It would be terrific if you gave us some clue about what is wrong in PEP355, so
that the next guy does not waste his time. For instance, I find
On 9/30/06, Terry Reedy <[EMAIL PROTECTED]> wrote:
>
> "Nick Coghlan" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
> >I suspect the problem would typically stem from floating point values that
> >are
> >read in from a human-readable file rather than being the result of a
> >'calcul
I am working on PEP 352 stuff for 2.6 and there are two changes that I think should be made that are not explicitly laid out in the PEP.First, and most dramatic, involves what is legal to list in an 'except' clause. Right now you can listing *anything*. This means ``except 42`` is totally legal e
Christos Georgiou wrote:
> Does anyone know why this happens? I can't find any information pointing to
> this being deliberate.
>
> I just upgraded to 2.5 on Windows (after making sure I can build extensions
> with the freeware VC++ Toolkit 2003) and some of my programs stopped
> operating. I s
"Nick Coghlan" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
>I suspect the problem would typically stem from floating point values that
>are
>read in from a human-readable file rather than being the result of a
>'calculation' as such:
For such situations, one could create a trans
Hi,
Just an opinion, but many uses of the ‘while true loop’
are instances of a ‘do loop’. I appreciate the language layout
question, so I’ll give you an alternative:
do:
while
Cheers,
Hans Polak.
This message contains informat
OK. Pronouncement: PEP 355 is dead. The authors (or the PEP editor)
can update the PEP.
I'm looking forward to a new PEP.
--Guido
On 9/30/06, Michael Hudson <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] writes:
>
> > I hope that eventually Python will include some form of OO
> > filesystem acce
[EMAIL PROTECTED] writes:
> I hope that eventually Python will include some form of OO
> filesystem access, but I am equally hopeful that the current PEP 355
> path.py is not it.
I think I agree with this too. For another source of ideas there is
the 'py.path' bit of the py lib, which, um, doesn
Well, a lot of extension code, like ours use PyFloat_FromDouble(foo); This can
be from vectors and stuff. Very often these are values from a database.
Integral float values are very common in such case and id didn't occur to me
that they weren't being reused, at least for small values.
Also,
""Martin v. Löwis"" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Please submit a bug report to sf.net/projects/python.
Done: www.python.org/sf/1568240
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/l
Martin v. Löwis wrote:
> Bob Ippolito schrieb:
>> My guess is that people do have this problem, they just don't know
>> where that memory has gone. I know I don't count objects unless I have
>> a process that's leaking memory or it grows so big that I notice (by
>> swapping or chance).
>
> Right.
Bob Ippolito schrieb:
> My guess is that people do have this problem, they just don't know
> where that memory has gone. I know I don't count objects unless I have
> a process that's leaking memory or it grows so big that I notice (by
> swapping or chance).
Right. Although I do wonder what kind of
Christos Georgiou schrieb:
> Does anyone know why this happens? I can't find any information pointing to
> this being deliberate.
It may well be that Tix wasn't included on Windows. I don't test Tix
regularly, and nobody reported missing it during the beta test.
Please submit a bug report to sf.
Jason Orendorff wrote:
> On 9/29/06, Fredrik Lundh <[EMAIL PROTECTED]> wrote:
>
>>(I just checked the program I'm working on, and my analysis tells me
>>that the most common floating point value in that program is 121.216,
>>which occurs 32 times. from what I can tell, 0.0 isn't used at all.)
>
Guido van Rossum wrote:
> On 9/29/06, A.M. Kuchling <[EMAIL PROTECTED]> wrote:
>
>>On Fri, Sep 29, 2006 at 09:49:35AM +0900, [EMAIL PROTECTED] wrote:
>>
>>>What is lost according to him is information about how the elements of
>>>a module work together. The docstrings tend to be narrowly focused
23 matches
Mail list logo
