diff options
| author | mattip <matti.picus@gmail.com> | 2019-10-17 11:16:57 +0300 |
|---|---|---|
| committer | mattip <matti.picus@gmail.com> | 2019-10-17 19:31:06 +0300 |
| commit | 0b474e3ee75d1086379e5f3e5cfc75594bbe56fc (patch) | |
| tree | ec70241fcd646da7ec82fce8412df5c7fedbe033 /doc/source/release | |
| parent | f8b9ba9c971c32c04b26cf9356fcb652fa754064 (diff) | |
| download | numpy-0b474e3ee75d1086379e5f3e5cfc75594bbe56fc.tar.gz | |
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 166502ac5..71fcb77c3 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 |