[Python-Dev] Stdlib and timezones, again
Antoine Pitrou
solipsis at pitrou.net
Mon Oct 1 16:12:26 CEST 2012
More information about the Python-Dev mailing list
Mon Oct 1 16:12:26 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 16:06:18 +0200 Lennart Regebro <regebro at gmail.com> wrote: > Actually, that's not a bad idea. My original idea was to warn if it *was* > outdated, but since there is no way to check that, I scratched that idea. > But as I have pointed out several times, a database that is shipped with > Python is almost guaranteed to be outdated, so yeah, we could just warn > *all the time*. :-) > > I like this idea. It gives an incentive to update: Get rid of the annoying > warning. Well, no, it is just silly. If we ship a database, that's because we think it is good enough. A warning is just a nuisance here. We don't display warnings when the installed Python version is too old. 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