clusterman
clusterman copied to clipboard
Bump arrow from 0.14.6 to 0.15.1
Bumps arrow from 0.14.6 to 0.15.1.
Release notes
Sourced from arrow's releases.
Version 0.15.1
- [FIX] Fixed a bug that caused Arrow to fail when passed a negative timestamp string.
- [FIX] Fixed a bug that caused Arrow to fail when passed a datetime object with
tzinfoof typeStaticTzInfo.Version 0.15.0
- [NEW] Added support for DDD and DDDD ordinal date tokens. The following functionality is now possible:
arrow.get("1998-045"),arrow.get("1998-45", "YYYY-DDD"),arrow.get("1998-045", "YYYY-DDDD").- [NEW] ISO 8601 basic format for dates and times is now supported (e.g.
YYYYMMDDTHHmmssZ).- [NEW] Added
humanizeweek granularity translations for French, Russian and Swiss German locales.- [CHANGE] Timestamps of type
strare no longer supported without a format string in thearrow.get()method. This change was made to support the ISO 8601 basic format and to address bugs such as #447.# will NOT work in v0.15.0 arrow.get("1565358758") arrow.get("1565358758.123413")will work in v0.15.0
arrow.get("1565358758", "X") arrow.get("1565358758.123413", "X") arrow.get(1565358758) arrow.get(1565358758.123413)
- [CHANGE] When a meridian token (a|A) is passed and no meridians are available for the specified locale (e.g. unsupported or untranslated) a
ParserErroris raised.- [CHANGE] The timestamp token (
X) will now match float timestamps of typestr:arrow.get(“1565358758.123415”, “X”).- [CHANGE] Strings with leading and/or trailing whitespace will no longer be parsed without a format string. Please see the docs for ways to handle this.
- [FIX] The timestamp token (
X) will now only match on strings that strictly contain integers and floats, preventing incorrect matches.- [FIX] Most instances of
arrow.get()returning an incorrectArrowobject from a partial parsing match have been eliminated. The following issue have been addressed: #91, #196, #396, #434, #447, #456, #519, #538, #560.Version 0.14.7
- [CHANGE]
ArrowParseWarningwill no longer be printed on every call toarrow.get()with a datetime string. The purpose of the warning was to start a conversation about the upcoming 0.15.0 changes and we appreciate all the feedback that the community has given us!
Changelog
Sourced from arrow's changelog.
0.15.1 (2019-09-10)
- [NEW] Added
humanizeweek granularity translations for Japanese.- [FIX] Fixed a bug that caused Arrow to fail when passed a negative timestamp string.
- [FIX] Fixed a bug that caused Arrow to fail when passed a datetime object with
tzinfoof typeStaticTzInfo.0.15.0 (2019-09-08)
- [NEW] Added support for DDD and DDDD ordinal date tokens. The following functionality is now possible:
arrow.get("1998-045"),arrow.get("1998-45", "YYYY-DDD"),arrow.get("1998-045", "YYYY-DDDD").- [NEW] ISO 8601 basic format for dates and times is now supported (e.g.
YYYYMMDDTHHmmssZ).- [NEW] Added
humanizeweek granularity translations for French, Russian and Swiss German locales.- [CHANGE] Timestamps of type
strare no longer supported without a format string in thearrow.get()method. This change was made to support the ISO 8601 basic format and to address bugs such as[#447](https://github.com/arrow-py/arrow/issues/447) <https://github.com/arrow-py/arrow/issues/447>_.The following will NOT work in v0.15.0:
.. code-block:: python
>>> arrow.get("1565358758") >>> arrow.get("1565358758.123413")The following will work in v0.15.0:
.. code-block:: python
>>> arrow.get("1565358758", "X") >>> arrow.get("1565358758.123413", "X") >>> arrow.get(1565358758) >>> arrow.get(1565358758.123413)
- [CHANGE] When a meridian token (a|A) is passed and no meridians are available for the specified locale (e.g. unsupported or untranslated) a
ParserErroris raised.- [CHANGE] The timestamp token (
X) will now match float timestamps of typestr:arrow.get(“1565358758.123415”, “X”).- [CHANGE] Strings with leading and/or trailing whitespace will no longer be parsed without a format string. Please see
the docs <https://arrow.readthedocs.io/#regular-expressions>_ for ways to handle this.- [FIX] The timestamp token (
X) will now only match on strings that strictly contain integers and floats, preventing incorrect matches.- [FIX] Most instances of
arrow.get()returning an incorrectArrowobject from a partial parsing match have been eliminated. The following issue have been addressed:[#91](https://github.com/arrow-py/arrow/issues/91) <https://github.com/arrow-py/arrow/issues/91>,[#196](https://github.com/arrow-py/arrow/issues/196) <https://github.com/arrow-py/arrow/issues/196>,[#396](https://github.com/arrow-py/arrow/issues/396) <https://github.com/arrow-py/arrow/issues/396>,[#434](https://github.com/arrow-py/arrow/issues/434) <https://github.com/arrow-py/arrow/issues/434>,[#447](https://github.com/arrow-py/arrow/issues/447) <https://github.com/arrow-py/arrow/issues/447>,[#456](https://github.com/arrow-py/arrow/issues/456) <https://github.com/arrow-py/arrow/issues/456>,[#519](https://github.com/arrow-py/arrow/issues/519) <https://github.com/arrow-py/arrow/issues/519>,[#538](https://github.com/arrow-py/arrow/issues/538) <https://github.com/arrow-py/arrow/issues/538>,[#560](https://github.com/arrow-py/arrow/issues/560) <https://github.com/arrow-py/arrow/issues/560>_.0.14.7 (2019-09-04)
- [CHANGE]
ArrowParseWarningwill no longer be printed on every call toarrow.get()with a datetime string. The purpose of the warning was to start a conversation about the upcoming 0.15.0 changes and we appreciate all the feedback that the community has given us!
Commits
96e19e8Merge pull request #665 from jadchaar/version-0.15.15b0d2a7Merge pull request #664 from jadchaar/tzinfo-zone15fae21Prep 0.15.1 releasef49cd84Renamed variabledafdb69Fix bug with tzinfo.zone256e53fMerge pull request #663 from JBKahn/patch-11974316linting45d12d4Update parser_tests.pyd856efaUpdate parser.py9b05216Add Japanese translations for week(s) (#659)- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)@dependabot use these labelswill set the current labels as the default for future PRs for this repo and language@dependabot use these reviewerswill set the current reviewers as the default for future PRs for this repo and language@dependabot use these assigneeswill set the current assignees as the default for future PRs for this repo and language@dependabot use this milestonewill set the current milestone as the default for future PRs for this repo and language
You can disable automated security fix PRs for this repo from the Security Alerts page.