diff options
| author | Tim Peters <tim.peters@gmail.com> | 2003-01-23 20:53:10 (GMT) |
|---|---|---|
| committer | Tim Peters <tim.peters@gmail.com> | 2003-01-23 20:53:10 (GMT) |
| commit | 2a44a8d3320ee7bcf5d718b5bdac550c6d34db4c (patch) | |
| tree | 7ac5d610e87d7a2b56e097e14525d9bc3182459f /Misc | |
| parent | 10cadce41ec7b94aafc11b4f2c9cfb7587f5b81d (diff) | |
| download | cpython-2a44a8d3320ee7bcf5d718b5bdac550c6d34db4c.zip cpython-2a44a8d3320ee7bcf5d718b5bdac550c6d34db4c.tar.gz cpython-2a44a8d3320ee7bcf5d718b5bdac550c6d34db4c.tar.bz2 | |
SF bug 660872: datetimetz constructors behave counterintuitively (2.3a1).
This gives much the same treatment to datetime.fromtimestamp(stamp, tz) as
the last batch of checkins gave to datetime.now(tz): do "the obvious"
thing with the tz argument instead of a senseless thing.
Diffstat (limited to 'Misc')
| -rw-r--r-- | Misc/NEWS | 4 |
1 files changed, 4 insertions, 0 deletions
@@ -93,6 +93,10 @@ Extension modules a tz argument, now() continues to return the current local date and time, as a naive datetime object. + datetime.fromtimestamp(): Like datetime.now() above, this had less than + useful behavior when the optional tinzo argument was specified. See + also SF bug report <http://www.python.org/sf/660872>. + The constructors building a datetime from a timestamp could raise ValueError if the platform C localtime()/gmtime() inserted "leap seconds". Leap seconds are ignored now. On such platforms, it's |