Revisions of python3-python-dateutil
Sebastian Wagner (sebix)
committed
(revision 17)
- update to version 2.8.2:
- Data updates:
- Updated tzdata version to 2021a. (gh pr #1128)
- Bugfixes:
- Fixed a bug in the parser where non-``ValueError`` exceptions would be raised
during exception handling; this would happen, for example, if an
``IllegalMonthError`` was raised in ``dateutil`` code. Fixed by Mark Bailey.
(gh issue #981, pr #987).
- Fixed the custom ``repr`` for ``dateutil.parser.ParserError``, which was not
defined due to an indentation error. (gh issue #991, gh pr #993)
- Fixed a bug that caused ``b'`` prefixes to appear in parse_isodate exception
messages. Reported and fixed by Paul Brown (@pawl) (gh pr #1122)
- Make ``isoparse`` raise when trying to parse times with inconsistent use of
`:` separator. Reported and fixed by @mariocj89 (gh pr #1125).
- Fixed ``tz.gettz()`` not returning local time when passed an empty string.
Reported by @labrys (gh issues #925, #926). Fixed by @ffe4 (gh pr #1024)
- Documentation changes:
- Rearranged parser documentation into "Functions", "Classes" and "Warnings and
Exceptions" categories. (gh issue #992, pr #994).
- Updated ``parser.parse`` documentation to reflect the switch from
``ValueError`` to ``ParserError``. (gh issue #992, pr #994).
- Fixed methods in the ``rrule`` module not being displayed in the docs. (gh pr
#1025)
- Changed some relative links in the exercise documentation to refer to the
document locations in the input tree, rather than the generated HTML files in
the HTML output tree (which presumably will not exist in non-HTML output
formats). (gh pr #1078).
- Misc:
- Moved ``test_imports.py``, ``test_internals.py`` and ``test_utils.py`` to
pytest. Reported and fixed by @jpurviance (gh pr #978)
Sebastian Wagner (sebix)
committed
(revision 2)
- Don't provide python2-dateutil, singlespec packages should use
correct name.
- Converted to single-spec
- Enabled tests
- Spec cleanup
- Use https for Source
- Update to version 2.6.0
* Added PEP-495-compatible methods to address ambiguous and
imaginary dates in time zones in a backwards-compatible
way. Ambiguous dates and times can now be safely represented
by all dateutil time zones. Many thanks to Alexander
Belopolski (@abalkin) and Tim Peters @tim-one for their
inputs on how to address this. Original issues reported by
Yupeng and @zed (lP: 1390262, gh issues #57, #112, #249,
#284, #286, prs #127, #225, #248, #264, #302).
* Added new methods for working with ambiguous and imaginary
dates to the tz module. datetime_ambiguous() determines if
a datetime is ambiguous for a given zone and datetime_exists()
determines if a datetime exists in a given zone.
This works for all fold-aware datetimes, not just those
provided by dateutil. (gh issue #253, gh pr #302)
* Fixed an issue where dst() in Portugal in 1996 was
returning the wrong value in tz.tzfile objects. Reported
by @abalkin (gh issue #128, pr #225)
* Fixed an issue where zoneinfo.ZoneInfoFile errors were not
being properly deep-copied. (gh issue #226, pr #225)
* Refactored tzwin and tzrange as a subclass of a common
Sebastian Wagner (sebix)
committed
(revision 1)
Displaying all 17 revisions
