Nick Coghlan <[EMAIL PROTECTED]> wrote in
news:[EMAIL PROTECTED]:
> Duncan Booth wrote:
>> I'm not convinced by the rationale given why atime,ctime,mtime and
>> size are methods rather than properties but I do find this PEP much
>> more agreeable than the last time I looked at it.
>
> A better r
Duncan Booth wrote:
> I'm not convinced by the rationale given why atime,ctime,mtime and size are
> methods rather than properties but I do find this PEP much more agreeable
> than the last time I looked at it.
A better rationale for doing it is that all of them may raise IOException.
It's rude
BJörn Lindqvist <[EMAIL PROTECTED]> wrote in
news:[EMAIL PROTECTED]:
> On 2/4/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
>> I won't even look at the PEP as long as it uses / or // (or any other
>> operator) for concatenation.
>
> That's good, because it doesn't. :)
> http://www.python.org/p
BJörn Lindqvist wrote:
> On 2/4/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
>> I won't even look at the PEP as long as it uses / or // (or any other
>> operator) for concatenation.
>
> That's good, because it doesn't. :) http://www.python.org/peps/pep-0355.html
My mistake - that's been signif
On 2/4/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> I won't even look at the PEP as long as it uses / or // (or any other
> operator) for concatenation.
That's good, because it doesn't. :) http://www.python.org/peps/pep-0355.html
--
mvh Björn
___
P
I won't even look at the PEP as long as it uses / or // (or any other
operator) for concatenation.
On 2/3/06, Nick Coghlan <[EMAIL PROTECTED]> wrote:
> I was tinkering with something today, and wondered whether it would cause
> fewer objections if the PEP used the floor division operator (//) to c
I was tinkering with something today, and wondered whether it would cause
fewer objections if the PEP used the floor division operator (//) to combine
path fragments, instead of the true division operator?
The parallel to directory separators is still there, but the syntax isn't tied
quite so s
