On Mon, Aug 24, 2015 at 4:28 PM, ISAAC J SCHWABACHER <[email protected]> wrote:
> [ijs] > I *really* hope the answer to this one is, "don't do that". > That's not an option because people already *do* [1] that and they won't stop. Neither they will stop using datetime.combine() [2] or datetime.replace() [3] or tolerate if those methods start raising exceptions. I am giving examples from datetime.py which in theory we can change, but what we use in datetime.py is likely to be used in user code as well. [1]: https://hg.python.org/cpython/file/v3.5.0rc1/Lib/datetime.py#l1476 [2]: https://hg.python.org/cpython/file/v3.5.0rc1/Lib/datetime.py#l1734 [3]: https://hg.python.org/cpython/file/v3.5.0rc1/Lib/datetime.py#l1540
_______________________________________________ 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/
