<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Aug 24, 2015 at 4:28 PM, ISAAC J SCHWABACHER <span dir="ltr"><<a href="mailto:ischwabacher@wisc.edu" target="_blank">ischwabacher@wisc.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class="gmail_extra">[ijs]<br>
I *really* hope the answer to this one is, "don't do that".</div></blockquote></div><br>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.</div><div class="gmail_extra"><br></div><div class="gmail_extra">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.</div><div class="gmail_extra"><br></div><div class="gmail_extra">[1]: <a href="https://hg.python.org/cpython/file/v3.5.0rc1/Lib/datetime.py#l1476">https://hg.python.org/cpython/file/v3.5.0rc1/Lib/datetime.py#l1476</a></div><div class="gmail_extra">[2]: <a href="https://hg.python.org/cpython/file/v3.5.0rc1/Lib/datetime.py#l1734">https://hg.python.org/cpython/file/v3.5.0rc1/Lib/datetime.py#l1734</a></div><div class="gmail_extra">[3]: <a href="https://hg.python.org/cpython/file/v3.5.0rc1/Lib/datetime.py#l1540">https://hg.python.org/cpython/file/v3.5.0rc1/Lib/datetime.py#l1540</a></div></div>