Forums
New posts
Search forums
Members
Current visitors
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Forums
Archive
Archive
Python
finding file size
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
[QUOTE="Gerrit Holl, post: 1744585"] [Peter Otten] [Gerrit Holl (me)] [Mike C. Fletcher] Sure, I don't think os.path would die soon, it will surely take longer than the string module to die. But I think there is a number of places where Python could be more object-oriented than it is, and this is one of them. The first step in making those modules more object-oriented is providing a OO-alternative: the second step is deprecating the old way, and the third step is providing only the OO-way. The third step will surely not be made until Python 3.0. The string module has made the first two steps. In my view, the time module has made the first step, although I'm not sure whether that's true. I would like to see a datetime module that makes the time module totally reduntant, because I never liked the time module: it doesn't fit into my brain properly, because it's not object oriented. Now, I try to use the datetime module whenever I can, but something like strptime isn't there. PEP 321 solves this, so I'd like time to become eventually deprecated after something DateUtil-like inclusion as well, but it probably won't. Hmm, the Zen of Python is not very clear about this: Now is better than never. Although never is often better than *right* now. ....so there must be a difference between 'now' and 'right now' :) Sure :) yours, Gerrit. [/QUOTE]
Verification
Post reply
Forums
Archive
Archive
Python
finding file size
Top