summaryrefslogtreecommitdiff
path: root/doc/source/reference/arrays.datetime.rst
Commit message (Collapse)AuthorAgeFilesLines
* DIC: Misc RST reformatting.Matthias Bussonnier2022-06-031-2/+2
| | | | | | | | | | | | | | | | | | | | | This contains various RST reformatting. One, moving `(C)` one line up, is specific to a bug in tree-sitter-rst that mis parses this section. Another is adding one black line for a similar reason where `..` is seen as section underline by tree-sitter-rst. This is some shuffling of section underline: try to be consitant, `=`, then `-`, then `~`, with this refactor there is also no more section that use backticks as underline. Note in particular that non-consitency of underline lead to a problem in datetime64 section where "weekmasks" (underlined with `-`) were actually a level-4 heading instead of a level 2 or 3 I guess, and thus were nested under the `busday_count()` section. You'll note also 2 formulas that are under double-quotes as they are not references.
* DOC: explicitly define numpy.datetime64 semanticsStefano Miccoli2022-01-101-18/+111
| | | | | | | | | | | | | Explicity state datetime64 semantics: - adoption of proleptic Gregorian Calendar - Astronomical year numbering - 86400 s constant length of day. Add some exmples of shortcomings of the above semnatics with ref. to UTC timescale (missing leap seconds) and UT timescale (variable legth of day). Closes GH-20675
* DOC: add example showing how to convert POSIX timestamps to datetime64 (#18984)Jonathan Reichelt Gjertsen2021-10-011-3/+15
| | | | | * DOC: add example showing how to convert POSIX timestamps to datetime64 Co-authored-by: Melissa Weber Mendonça <melissawm@gmail.com>
* DOC resolves #14299 rephrasingKasia2021-05-091-3/+4
|
* DOC: resolves #14299 - deleting the noteKasia2021-05-091-3/+1
|
* DOC: Improve datetime64 docs #14299Kasia2021-05-091-1/+1
|
* DOC: Improve datetime64 docs #14299Kasia2021-05-091-3/+8
|
* ENH: Allow μs as an alias for usEric Wieser2020-08-281-1/+1
| | | | This is motivated primarily as a proof that the datetime API is now unicode-safe, and generally seems harmless.
* Update doc/source/reference/arrays.datetime.rstPierre de Buyl2020-03-061-2/+1
| | | Co-Authored-By: Eric Wieser <wieser.eric@gmail.com>
* DOC: move deprecation info to apart paragraph.Pierre de Buyl2020-03-061-4/+8
|
* reinstate example with offsetPierre de Buyl2020-03-061-0/+2
|
* DOC: remove outdated example and sectionPierre de Buyl2020-03-061-51/+20
| | | | | | Remove example with timezone Remove section on changes in NumPy 1.11
* TST: run refguide-check on rst files in doc/*mattip2019-10-171-3/+3
|
* DOC: include NAT value and remove Differences between 1.6 and 1.7 Datetimes ↵Andrew Liu2019-09-121-131/+28
| | | | section
* DOC: add timedelta64 signatureAndrew Liu2019-09-101-1/+3
|
* ENH: add timedelta modulusTyler Reddy2018-10-151-0/+3
| | | | | | * added support for modulus operator with timedelta operands; type signature is mm->m
* DOC: BLD: fix lots of Sphinx warnings/errors.Ralf Gommers2017-06-101-1/+2
|
* DOC: Fix typosJakub Wilk2017-03-171-2/+2
|
* DOC: Corrections in Datetime Units-arrays.datetime.rstbadhrink2016-06-101-3/+3
| | | | | Changed/corrected Time span - relative and absolute - for second, millisecond and microsecond. There were slight differences and was noted duly in the issue. See #6711 (https://github.com/numpy/numpy/issues/6711)
* API: Make datetime64 timezone naiveStephan Hoyer2016-01-151-25/+37
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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')
* STY: Giant whitespace cleanup.Charles Harris2013-08-181-1/+1
| | | | Now is as good a time as any with open PR's at a low.
* DOC: Add a section documenting 1.6/1.7 datetime64 differencesMark Wiebe2012-05-011-0/+127
|
* DOC: label datetime support as experimental. Closes #2072.Ralf Gommers2012-03-301-0/+3
|
* DOC: datetime: Update the docs to reflect busday_count changeMark Wiebe2011-07-191-2/+1
|
* DOC: datetime: hyperlink busday_count and is_busday functions in datetime docMark Wiebe2011-07-191-2/+2
|
* DOC: datetime: Add additional tutorial information.Steve R. Hastings2011-07-191-27/+95
|
* DOC: fix build issues (with latex or newest sphinx)Pauli Virtanen2011-07-151-11/+7
|
* DOC: datetime: Split the date/time units into two separate tablesMark Wiebe2011-07-011-7/+24
|
* DOC: datetime: Updates based on Chuck's feedbackMark Wiebe2011-07-011-6/+16
|
* DOC: datetime: Start a draft of introductory datetime documentationMark Wiebe2011-07-011-0/+261
View Lorry Controller Status