diff options
| author | Stephan Hoyer <shoyer@climate.com> | 2016-01-14 23:47:37 -0800 |
|---|---|---|
| committer | Stephan Hoyer <shoyer@climate.com> | 2016-01-15 16:18:46 -0800 |
| commit | 426114879da49bf9a586b1991dcaf38ce594c4b6 (patch) | |
| tree | 17a3342488f493ed410eaa9798a84d15bb63047d /numpy/testing/utils.py | |
| parent | d588b48a0e2fd4a78cadc1336571f59ba6be83c6 (diff) | |
| download | numpy-426114879da49bf9a586b1991dcaf38ce594c4b6.tar.gz | |
API: Make datetime64 timezone naive
Fixes GH3290
With apologies to mwiebe, this rips out most of the time zone parsing from
the datetime64 type.
I think we mostly sorted out the API design in discussions last year, but
I'll be posting this to the mailing list shortly to get feedback.
Old behavior:
# string parsing and printing defaults to your local timezone :(
>>> np.datetime64('2000-01-01T00')
numpy.datetime64('2000-01-01T00:00-0800','h')
New behavior:
# datetime64 is parsed and printed as timezone naive
>>> np.datetime64('2000-01-01T00')
numpy.datetime64('2000-01-01T00','h')
# you can still supply a timezone, but you get a deprecation warning
>>> np.datetime64('2000-01-01T00Z')
DeprecationWarning: parsing timezone aware datetimes is deprecated; this
will raise an error in the future
numpy.datetime64('2000-01-01T00','h')
Diffstat (limited to 'numpy/testing/utils.py')
0 files changed, 0 insertions, 0 deletions