On 09/01/2014 16:01, Ethan Furman wrote:
On 01/09/2014 12:42 AM, Mark Lawrence wrote:
On 09/01/2014 01:27, Roy Smith wrote:
Naive datetimes are what everybody uses. It's what utcnow() gives you.
So why make life difficult for everybody? Python 3 didn't win a convert
today.
Yep, dates and times are easy. That's why there are 17 issues open on
the bug tracker referencing tzinfo alone. Poor
old 1100942 is high priority, was created 12/01/2005 and has missed
3.4. So if it gets into 3.5 it'll have already
celebrated its 10th birthday. It doesn't say much for the amount of
effort that we put into looking after issues.
Mark, I hope you are addressing the community at large and not the
core-devs. There are only so many of us, with limited time available.
--
~Ethan~
As I'm not a core dev to whom do you think I'm referring? I'm aware
that the high horse I get on about this is so tall that you'll need an
oxygen supply to survive should you want to sit on it, but to me this is
easily the worst aspect of the Python community as a whole. If every
regular contributor to this list was to fix even one bug a week the
figures would look rather better. Still, you can no more enforce that
than you can enforce the core devs working on Python 2.8 :)
Talking of which, have we got a PEP for that yet, or are the whingers
still simply in whinging mode?
--
My fellow Pythonistas, ask not what our language can do for you, ask
what you can do for our language.
Mark Lawrence
--
https://mail.python.org/mailman/listinfo/python-list
