diff options
| author | Charles Harris <charlesr.harris@gmail.com> | 2019-11-23 07:40:59 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-11-23 07:40:59 -0800 |
| commit | d76efa771b4915f4e3f5aa2023bb50e46c41b4bc (patch) | |
| tree | f3625f42df57393bf8e08a9f67658252a7dd33b8 /doc/source/release | |
| parent | 2f2fa20b95d1da4ea11fb78a8071787d626b39a3 (diff) | |
| parent | dff3c1f90af9053128e6e241e1b5f19d858670f4 (diff) | |
| download | numpy-d76efa771b4915f4e3f5aa2023bb50e46c41b4bc.tar.gz | |
Merge pull request #14732 from mattip/refguide-rst
TST: run refguide-check on rst files in doc/*
Diffstat (limited to 'doc/source/release')
| -rw-r--r-- | doc/source/release/1.11.0-notes.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/source/release/1.11.0-notes.rst b/doc/source/release/1.11.0-notes.rst index 1a179657b..36cd1d65a 100644 --- a/doc/source/release/1.11.0-notes.rst +++ b/doc/source/release/1.11.0-notes.rst @@ -85,7 +85,7 @@ times in UTC. By default, creating a datetime64 object from a string or printing it would convert from or to local time:: # old behavior - >>>> np.datetime64('2000-01-01T00:00:00') + >>> np.datetime64('2000-01-01T00:00:00') numpy.datetime64('2000-01-01T00:00:00-0800') # note the timezone offset -08:00 @@ -96,7 +96,7 @@ type is preferred, similar to the ``datetime.datetime`` type in the Python standard library. Accordingly, datetime64 no longer assumes that input is in local time, nor does it print local times:: - >>>> np.datetime64('2000-01-01T00:00:00') + >>> np.datetime64('2000-01-01T00:00:00') numpy.datetime64('2000-01-01T00:00:00') For backwards compatibility, datetime64 still parses timezone offsets, which |