python-cftime
No description set
- Developed at devel:languages:python
- Sources inherited from project openSUSE:Factory
-
3
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout home:adrianSuSE:PL/python-cftime && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
cftime-1.6.0.tar.gz | 0000047633 46.5 KB | |
python-cftime.changes | 0000008198 8.01 KB | |
python-cftime.spec | 0000001954 1.91 KB |
Revision 6 (latest revision is 11)
Dominique Leuenberger (dimstar_suse)
accepted
request 965204
from
Dirk Mueller (dirkmueller)
(revision 6)
- update to 1.6.0: * fix for masked array inputs * improved performance of the num2date algorithm, in some cases providing an over 100x speedup * fix for date2index for select != 'exact' when select='exact' works * silently change calendar='gregorian' to 'standard' internally, since 'gregorian' deprecated in CF v1.9 * add "is_leap_year" function * wheels that work on Apple M1 (arm64) available on pypi. * added support for "common_year" and "common_years" units for "noleap" and "365_day" calendars * check consistency of year arg and has_year_zero kwarg in cftime.datetime (issue #248). Also assume if has_year_zero not specified it should be True if year=0. Allow replace method to change has_year_zero. Issue UserWarning if year set to zero and calendar default is changed from False to True (so that user is aware the resulting instance will not be CF compliant). * '360_day' was missing from list of 'idealized' calendars. * fixed a bug that led to subclasses losing their type identity upon pickling * Change default behavior of proleptic_gregorian to has_year_zero=T (to be consistent with ISO-8601 since CF does not specify the year zero convention for this calendar). Issue warning when trying to to create a cftime.datetime instance that is not allowed in CF * clean-up deprecated calendar specific subclasses * added string formatting support to `cftime.datetime` objects (via `cftime.datetime.__format__`) * add support for astronomical year numbering (including year zero) for real-world calendars using 'has_year_zero' cftime.datetime kwarg Default is False for 'real-world' calendars ('julian', 'gregorian'/'standard', 'proleptic_gregorian'). Ignored for idealized calendars like '360_day
Comments 0