[Python-Dev] Stdlib and timezones, again
Antoine Pitrou
solipsis at pitrou.net
Mon Oct 1 17:03:25 CEST 2012
More information about the Python-Dev mailing list
Mon Oct 1 17:03:25 CEST 2012
- Previous message: [Python-Dev] Stdlib and timezones, again
- Next message: [Python-Dev] Stdlib and timezones, again
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, 1 Oct 2012 09:52:09 -0500 Zachary Ware <zachary.ware+pydev at gmail.com> wrote: > > My thought was that it's better to have *something* always available, > that has a decent chance of being "good enough" in a lot of cases (and > if it's good enough for you, just silence the warning), than to > noisily fail because we can't provide a perfect solution due to > political idiocy. Or worse, to *silently* be wrong because someone > assumed we had provided a perfect solution without looking too hard. We can, and should, mention potential pitfalls in the documentation. But I don't think a warning is warranted, anymore than for other known issues (there are many of them at http://bugs.python.org/ :-)). Regards Antoine. -- Software development and contracting: http://pro.pitrou.net
- Previous message: [Python-Dev] Stdlib and timezones, again
- Next message: [Python-Dev] Stdlib and timezones, again
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list