On Thu, Sep 3, 2015 at 11:42 AM, Carl Meyer <[email protected]> wrote:
> There is an alternative solution available that avoids this problem, and > all other inconsistencies. > Really? PEP 495 has a more or less complete reference implementation in my github fork [1] of cpython. I have recently added the hash invariant preservation rule which required a change to the grand total of two lines in datetime.py. Something that is that easy to implement cannot be too hard to explain and document. I would like to specifically point out that the only existing unit test that my patch has to modify is the one which checks that astimezone() method raises an exception on a naive datetime. I have not seen any "alternative solution" implemented anywhere. If you have not tried it yourself - trust me - keeping 4000+ lines of unit tests intact while adding features to the datetime module is not an easy task. [1]: https://github.com/abalkin/cpython/tree/issue24773
_______________________________________________ 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/
