Re:Recharging the Python standard library
by Daishiman on Friday October 11, 2013 @02:07PM
(#6534804)
If I may ask, what's wrong with datetime? I may not have encountered unusual cases, but for most uses the date + datetime + timedelta scheme seems to work pretty well.
Re:Recharging the Python standard library
by falcolas on Friday October 11, 2013 @02:13PM
(#6534853)
I don't think anything is wrong with datetime - it's just a stdlib tool that I use on a regular basis. Sorry, wasn't listing just those I think have warts or those replaced by other tools, just libs that I use regularly.
My only gripe with datetime and time are the organization of it. I can never remember whether it's datetime.datetime.now or datetime.now or time.timedelta or datetime.timedelta, and so on.
Re:Recharging the Python standard library
by falcolas on Friday October 11, 2013 @05:21PM
(#6535997)
Yeah, typing datetime.datetime for everything gets pretty old.
I just remember that datetime is the package, datetime.datetime is the class, and datetime.datetime.now() is a @classmethod that returns instances of that class. I do kinda wish it was datetime.now() for the constructor instead.
To refer back to the "old batteries" argument, the included batteries may be the old lead acid type, but they're dependable in a lot of cases where newer lithium ion batteries would rather catch fire.