Nice. One thought: why do you call it arrow? I know you can call it anything you want, but one reason requests is so popular because the name totally makes sense. My little 0.2 is why not rename it to pydate or something more intuitive.
What's the difference between .utcnow() and .now()? Is one supposed to be an alias or is .now() default to the time the platform is set to?
I've opened an issue regarding calling convention. What do HNer think?
The other commenters here are correct, it is a reference to Time's Arrow (the book, or Star Trek: TNG episode), and other directional time metaphors :)
Comments
Nice. One thought: why do you call it arrow? I know you can call it anything you want, but one reason requests is so popular because the name totally makes sense. My little 0.2 is why not rename it to pydate or something more intuitive.
What's the difference between .utcnow() and .now()? Is one supposed to be an alias or is .now() default to the time the platform is set to?
I've opened an issue regarding calling convention. What do HNer think?
https://github.com/crsmithdev/arrow/issues/125
I presume it's a reference to https://en.wikipedia.org/wiki/Arrow_of_time.
The other commenters here are correct, it is a reference to Time's Arrow (the book, or Star Trek: TNG episode), and other directional time metaphors :)
I imagine it's because of "time flies like an arrow".
"fruit flies like a bannana"
utcnow() is the current time in the UTC timezone with not timezone attached, now() is based on the timezone your machine is set to.