|
|
|
|
Changelog for python312-cftime-1.6.4-27.17.x86_64.rpm :
* Sun Jun 09 2024 Ben Greiner - Update to 1.6.4 * return empty array if one provided to date2num (issue #315). * numpy 2.0 compatibility (issue #325). * handle nan/inf in num2date (issue #328).- Build PEP517 * Fri Dec 01 2023 Dirk Müller - update to 1.6.3: * add support for formats without separators in strptime (e.g. \'20200229\', issue #301). * set the c_api_binop_methods compiler directive to True to retain Cython 0.x behavior for arithmetic operators for Cython >= 3.0.0 * support for python 3.12.- drop cython3.patch (upstream) * Wed Aug 30 2023 Markéta Machová - add upstream cython3.patch * Thu Oct 27 2022 Yogalakshmi Arunachalam - Update to version 1.6.2 * num2date should not fail on an empty integer array (issue #287). * longdouble keyword in date2num so that a roundtrip from a time to a date and back again does not lose microsecond precision when the units require the times be encoded as floating point values (PR #284) * added strptime method (issue #277). * cibuildwheel wheel-building workflow added to github actions by AATTocefpaf (triggers binary wheel builds and uploads to pypi automatically when GH release created). PR #290. * Mon Sep 26 2022 Yogalakshmi Arunachalam - Update to version 1.6.1 * fix failing tests on windows with numpy 1.23.0 (issue #278) * expose to_tuple module function in public API. * Sun Mar 27 2022 Dirk Müller - 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 (they always have year zero). * add \"change_calendar\" cftime.datetime method to switch to another \'real-world\' calendar. Enable comparison of cftime.datetime instances with different \'real-world\' calendars (using the new change_calendar method) * remove legacy `utime` class, and legacy `JulianDayFromDate` and `DateFromJulianDay` functions (replaced by `cftime.datetime.toordinal` and `cftime.datetime.fromordinal`). * Change ValueError to TypeError in __sub__ * Tue Mar 02 2021 Steve Kowalik - Update to 1.4.1: * Restore use of calendar-specific sub-classes in `cftime.num2date`, `cftime.datetime.__add__`, and `cftime.datetime.__sub__`. The use of them will be removed in a later release. * add \'fromordinal\' static method to create a cftime.datetime instance from a julian day ordinal and calendar (inverse of \'toordinal\'). * `cftime.date2num` will now always return an array of integers, if the units and times allow. Previously this would only be true if the units were \'microseconds\' (PR #225). In other circumstances, as before, `cftime.date2num` will return an array of floats. * Rewrite of julian day/calendar functions (_IntJulianDayToCalendar and _IntJulianDayFromCalendar) to remove GPL\'ed code. cftime license changed to MIT (to be consistent with netcdf4-python). * Added datetime.toordinal() (returns julian day, kwarg \'fractional\' can be used to include fractional day). * cftime.datetime no longer uses calendar-specific sub-classes. * fix for issue #211 (PR #212) bug in masked array handling in date2num) * switch from travis/appveyor to github actions for CI/CD (PR #215). * switch to cython language_level=3 (no more support for python 2) (PR #217). * add __init__.py to test dir so pytest coverage works again. Add Coveralls step to github actions workflow to upload coverage data to coveralls.io (PR [#217]). * move package under \'src\' directory so cftime can be imported from install dir (PR #218 - see https://blog.ionelmc.ro/2014/05/25/python-packaging/#the-structure). * zero pad years in strtime (issue #194) * have cftime.datetime constuctor create \'calendar-aware\' instances (default is \'standard\' calendar, if calendar=\'\' or None the instance is not calendar aware and some methods, like dayofwk, dayofyr, __add__ and __sub__, will not work). Fixes issue #198. The calendar specific sub-classes are now deprecated, but remain for now as stubs that just instantiate the base class and override __repr__. * update regex in _cpdef _parse_date so reference years with more than four digits can be handled. * Change default calendar in cftime.date2num from \'standard\' to None (calendar associated with first input datetime object is used). * add `cftime.datetime.tzinfo=None` for compatibility with python datetime (issue #208). * num2date uses \'proleptic_gregorian\' scheme when basedate is post-Gregorian but date is pre-Gregorian (issue #182). * fix 1.2.0 regression (date2num no longer works with numpy scalar array inputs, issue #185). * Fix for issue #187 (have date2num round to the nearest second when within 1 microsecond). * Fix for issue #189 (leap years calculated incorrectly for negative years in proleptic_gregorian calendar).- No longer build for Python 3.6, due to no NumPy.- Correct license file name. * Thu Jul 09 2020 Steve Kowalik - Update to 1.2.0: * Return the default values of dayofwk and dayofyr when calendar is \'\' (issue #173). * fix treatment of masked arrays in num2date and date2num (issue #175). Also make sure masked arrays are output from num2date/date2num if masked arrays are input. * Where possible, use timedelta arithmetic to decode times exactly within num2date (issue #171). * Make taking the difference between two cftime datetimes to produce a timedelta exact to the microsecond; depending on the units encoding, this enables date2num to be exact as well (issue #109). * utime.date2num/utime.num2date now just call module level functions. JulianDayFromDate/DateFromJulianDay no longer used internally (PR #180). * add isoformat method for compatibility with python datetime (issue #152). * make \'standard\' default calendar for cftime.datetime so that dayofwk,dayofyr methods don\'t fail (issue #169). * change dayofwk and dayofyr attributes into properties (issue #158) * fix for issue #165 (python datetime should be returned when only_use_cftime_datimes=False). * include pyproject.toml in MANIFEST.in so it gets included in source tarball (issue #154). * fix microsecond formatting issue, ensure identical results computed for arrays and scales (issue #143, PR #146). * improved exceptions for time differences (issue #128, PR #131). * fix intersphinx entries (issue #133, PR #133) * make only_use_cftime_datetimes=True by default, so cftime datetime instances are returned by default by num2date (instead of returning python datetime instances where possible). Issue #136, PR #135. * Add daysinmonth attribute (issue #137, PR #138). * If only_use_python_datetimes=True and only_use_cftime_datetimes=False, num2date only returns python datetime instances and raises an exception if this is not possible. * Fix for fractional seconds in reference date in units string- Add numpy-devel to BuildRequires. * Fri Jan 24 2020 Marketa Calabkova - update to 1.0.4.2 * fix for date2num error when converting a DatetimeProlepticGregorian object * Thu Mar 07 2019 Tomáš Chvátal - Update to 1.0.3.4: * fixes for python2.7 * Various flake fixes * More tests * python 3.8 support
|
|
|