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. 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 Cheers, -Barry
signature.asc
Description: PGP signature
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
