Re:Delorean – datetime conversions in Python
by googletron on Wednesday January 23, 2013 @03:33PM
(#5105110)
So the library does a little bit more than just deal with shifting timezones which as you put can be a little annoying.
I would take a look at the docs and see what else the library can provide before you start quoting the interface incorrectly. :)
As for the name I considered other things most lead to namespace pollution. You are right I might be able to clear up the reference for people who dont know "Back to the Future" series.
Re:Delorean – datetime conversions in Python
by toyg on Wednesday January 23, 2013 @08:14PM
(#5106480)
Aren't you worried that someone, somewhere might actually still own the rights to that trademark, and might, one day, come to you and ask for money? After all, you're clearly exploiting the original trademark for your own gain.
I know, I know, we all love an '80s inside-joke, but I think this is just a bit too far.
(great lib btw, datetime has always been a bloody pain, for no good reason.)
Re:Delorean – datetime conversions in Python
by EliRivers on Wednesday January 23, 2013 @04:11PM
(#5105291)
Obscure? No way. Time-travel (i.e. changing times) was the first thing I thought of.
Re:Delorean – datetime conversions in Python
by dorkrawk on Wednesday January 23, 2013 @04:06PM
(#5105263)
> but calling 'Delorean' to convert times is totally obscure
Unlike calling 'pickle' to serialize...
Re:Delorean – datetime conversions in Python
by maw on Wednesday January 23, 2013 @05:02PM
(#5105580)
Although now we make and eat pickled vegetables because we like the taste, pickling was originally developed in order to enable vegetables to store longer. Calling a serializer "pickle" isn't unreasonable.
Re:Delorean – datetime conversions in Python
by derelk on Wednesday January 23, 2013 @07:47PM
(#5106382)
It's not unreasonable, but it's still obscure. Calling a time utility Delorean isn't unreasonable, despite also being obscure.
Re:Delorean – datetime conversions in Python
by notatoad on Wednesday January 23, 2013 @09:02PM
(#5106659)
And if i were on the mailing lists back whenever they came up with pickle, i would have told them it was a silly name too.
Re:Delorean – datetime conversions in Python
by SoftwareMaven on Wednesday January 23, 2013 @04:20PM
(#5105356)
It will only be non-descriptive if it doesn't catch on. See, for instance, Django, Pyramid, Twisted, etc. Twisted is a particularly good example, since it shares a similar analogy: Twisted could reference the twisted pair networks use; Delorean references a time-traveling vehicle.
Re:Delorean – datetime conversions in Python
by citadelgrad on Thursday January 24, 2013 @12:56PM
(#5110968)
The name is marketing and I'm sure we're all more likely to remember because we all have a real world association with that name and back to the future.
`return utc.localize(datetime.utcnow()).astimezone(est)` is maybe a little annoying to type out, but it's obvious what it does. `return Delorean(est)` doesn't make any sense at all.