docs for datetime units show incorrect time spans
See original GitHub issueThis can be seen in http://docs.scipy.org/doc/numpy/reference/arrays.datetime.html#datetime-units
The correct time spans should be:
s second +/- 2.9e11 years [2.9e11 BC, 2.9e11 AD]
ms millisecond +/- 2.9e8 years [ 2.9e8 BC, 2.9e8 AD]
us microsecond +/- 2.9e5 years [290301 BC, 294241 AD]
ns nanosecond +/- 292 years [ 1678 AD, 2262 AD]
rather than
s second +/- 2.9e12 years [ 2.9e9 BC, 2.9e9 AD]
ms millisecond +/- 2.9e9 years [ 2.9e6 BC, 2.9e6 AD]
us microsecond +/- 2.9e6 years [290301 BC, 294241 AD]
ns nanosecond +/- 292 years [ 1678 AD, 2262 AD]
Issue Analytics
- State:
- Created 8 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
TimeSpan Struct (System) | Microsoft Learn
A TimeSpan object represents a time interval (duration of time or elapsed time) that is measured as a positive or negative number of...
Read more >Time series / date functionality — pandas 1.5.2 documentation
Similar to datetime.timedelta from the standard library. Time spans: A span of time defined by a point in time and its associated frequency....
Read more >datetime — Basic date and time types — Python 3.11.1 ...
A duration expressing the difference between two date , time , or datetime instances to microsecond resolution.
Read more >Date and time in Google Sheets - Ablebits
Here we are, we've placed date and time to our cells. The next step is to format the information to display it the...
Read more >12.7 Date and Time Functions
Functions that expect time values usually accept datetime values and ignore the ... For information on the INTERVAL unit argument, see Temporal Intervals....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I don’t recommend that approach for the back and forth typical of numpy PRs, but noticed that the PR was against 1.7.x rather than master. Recently testing against older branches seems to fail, possibly because of changes in the travis tester and also the fact that appveyor is newer.
Take a look at the contributing guidelines: https://github.com/numpy/numpy/blob/master/CONTRIBUTING.md (and links there-in)
It’s a little more work to set started, but I think it’s definitely worthwhile to get git setup properly on your computer.