<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 29 Dec, 2012, at 5:48, Lennart Regebro <<a href="mailto:regebro@gmail.com">regebro@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div class="gmail_quote">On Fri, Dec 28, 2012 at 10:12 PM, Ronald Oussoren <span dir="ltr"><<a href="mailto:ronaldoussoren@mac.com" target="_blank">ronaldoussoren@mac.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><br>
On 28 Dec, 2012, at 21:23, Lennart Regebro <<a href="mailto:regebro@gmail.com">regebro@gmail.com</a>> wrote:<br>
<br>
> Happy Holidays! Here is the update of PEP 431 with the changes that emerged after the earlier discussion.<br>
<br>
</div>Why is the new timezone support added in a submodule of datetime?</blockquote><div><br>Because several people wanted it that way and nobody objected.<br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Adding the new<br>
function and exception to datetime itself wouldn't clutter the API that much</blockquote><div><br>It will make the datetime.py twice as long though, and the second longest module in the stdlib, beaten only by decimal.py. Perhaps this is not a problem.<br></div></div></blockquote><div><br></div>The module could be split into several modules in a package without affecting the public API if that would help with maintenance, simular to unittest. </div><div><br></div><div>Ronald</div><div><br></div></body></html>