[Python-Dev] Draft PEP for time zone support. (original) (raw)
Guido van Rossum guido at python.org
Wed Dec 12 04:51:50 CET 2012
- Previous message: [Python-Dev] Draft PEP for time zone support.
- Next message: [Python-Dev] cpython: expose TCP_FASTOPEN and MSG_FASTOPEN
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, Dec 11, 2012 at 7:19 PM, Barry Warsaw <barry at python.org> wrote:
On Dec 12, 2012, at 01:14 PM, Nick Coghlan wrote:
That's a backwards compatibility risk, though - many applications are likely coping just fine with the slightly corrupted time values, but would fall over if an exception was raised instead.
Right.
The default should probably be chosen so that the single argument form of these calls continues to behave the same in 3.4 as it does in 3.3, emitting a DeprecationWarning to say that the default behaviour is going to change in 3.5 (so the actual default would be sentinel value, in order to tell the difference between an explicit True being passed and relying on the default behaviour). +1
I don't think it's worth deprecating the old behavior.
-- --Guido van Rossum (python.org/~guido)
- Previous message: [Python-Dev] Draft PEP for time zone support.
- Next message: [Python-Dev] cpython: expose TCP_FASTOPEN and MSG_FASTOPEN
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]