FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

Prepare 2.8.1 release by pganssle · Pull Request #974 · dateutil/dateutil · GitHub

Prepare 2.8.1 release - #974

Merged
pganssle merged 1 commit into
dateutil:masterfrom
pganssle:release_2.8.1
Nov 3, 2019
Merged

pganssle merged 1 commit into
dateutil:masterfrom
pganssle:release_2.8.1

Conversation

pganssle commented Nov 3, 2019

Copy link
Copy Markdown
Member

Summary of changes

This updates the changelog for the 2.8.1 release, which includes the following changes:

Version 2.8.1 (2019-11-03)

Data updates

  • Updated tzdata version to 2019c.

Bugfixes

Tests

Documentation changes

  • Fixed many misspellings, typos and styling errors in the comments
    and documentation. Patch by Hugo van Kemenade (gh pr Fix typos #952).

Misc

If you are listed here and would like to make any changes, unfortunately I'm springing this on you quite late in the game, as I plan to make a release tonight some time between 2019-11-03T05:00Z and 2019-11-03T06:59Z because I find it funny to make a release during an ambiguous datetime in my current local time zone (America/New_York).

pganssle added this to the 2.8.1 milestone Nov 3, 2019
pganssle merged commit fc9b162 into dateutil:master Nov 3, 2019

jacobg commented Jun 25, 2021
edited
Loading

Copy link
Copy Markdown

This rare parse() KeyError occurred for me running dateutil 2.8.1 on Python 2.7 (Google App Engine). It doesn't seem like this bug is fixed.

This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants


Back | FazBrowse Home | New Git URL