[Python-Dev] Stdlib and timezones, again (original) (raw)
Antoine Pitrou solipsis at pitrou.net
Mon Oct 1 17:28:06 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 10:16:16 -0500 Zachary Ware <zachary.ware at gmail.com> wrote:
> > 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/ :-)). >
Just curious (and a bit off topic), what exactly does warrant a warning in Python? I've been messing around with it for a couple years (since shortly before 3.1, and always on 3.x) and I'm pretty sure I have yet to see a warning for anything. Which I suppose could be counted as a good thing...
We don't really have a well-defined policy, except for one warning category: DeprecationWarnings, whose purpose are quite clear. But they are now silenced by default :-)
Generally, warnings are not easy to deal with for the end-user, so we are reluctant to add any. We'd rather document annoyances and pitfalls; and, moreover, we try to design our APIs so that they don't have unexpected effects.
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 ]