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 for properties to do that, so it's better to make them methods instead.
That was a general guideline that came up the first time adding Path was
proposed - if the functionality involved querying or manipulating the actual
filesystem (and therefore potentially raising IOError), then it should be a
method. If the operation related solely to the string representation, then it
could be a property.
Cheers,
Nick.
--
Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
---------------------------------------------------------------
http://www.boredomandlaziness.org
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4