<br><br>
<div><span class="gmail_quote">On 8/27/07, <b class="gmail_sendername">Dieter Maurer</b> <<a href="mailto:dieter@handshake.de">dieter@handshake.de</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Andreas Jung wrote at 2007-8-26 21:23 +0200:<br>> ...<br>>If you can: use Python's datetime module. DateTime is broken in many ways.
<br><br>If it handles daytime saving and addition by some float days -- it will<br>not have any chance...<br><br>If it does not handle daytime saving -- then it misses an essential<br>use case...<br><br>Some problems come from the complexity of the real world and
<br>not from a particular implementation....<br><br><br><br>--<br>Dieter</blockquote>
<div> </div>
<div>In this case it seems that the complexity is being added by the DateTime implementation. When given an int number of days and a DateTime that has no time element, DateTime should not convert everything down to seconds and account for DST that happens to occur during the period.
</div>
<div> </div>
<div>When adding days + days, I'd expect to get a result that only considers days; not DST.</div>
<div>So I agree with your earlier post that DateTime should treat int and float addition differently. It should also probably look at the DateTime and revert to integer math if there is no time element present.</div>
<div> </div>
<div>- Eric</div>
<div> </div>
<div> </div><br> </div>