On 08/01/2015 12:09 PM, Alexander Belopolsky wrote:
On Sat, Aug 1, 2015 at 2:34 PM, Ethan Furman <[email protected]> wrote:
My goal here is to minimize the impact on the programs that are
already written and deployed.
Why is this even a problem? Already written programs will not be using the
new strict tzinfo.
They will if their tzinfo provider switches to tzstrict.
It is not our problem if a third-party library makes backwards incompatible
changes.
We will still be supporting all three types in the stlib: naive, aware, and
strict.
If this new 'strict' support still has buggy behaviour around time shifts, why
are we bothering?
--
~Ethan~
_______________________________________________
Datetime-SIG mailing list
[email protected]
https://mail.python.org/mailman/listinfo/datetime-sig
The PSF Code of Conduct applies to this mailing list:
https://www.python.org/psf/codeofconduct/
