Update arrow requirement from <1.0.0,>=0.8.0 to >=0.8.0,<2.0.0

[dependabot]

Updates the requirements on arrow to permit the latest version.

Release notes

Sourced from arrow's releases.

Version 1.0.3

[FIX] Updated internals to avoid issues when running mypy --strict. [FIX] Corrections to Swedish locale. [INTERNAL] Lowered required coverage limit until humanize month tests are fixed.

Changelog

Sourced from arrow's changelog.

1.0.3 (2021-03-05)

• [FIX] Updated internals to avoid issues when running mypy --strict.
• [FIX] Corrections to Swedish locale.
• [INTERNAL] Lowered required coverage limit until humanize month tests are fixed.

1.0.2 (2021-02-28)

• [FIXED] Fixed an OverflowError that could occur when running Arrow on a 32-bit OS.

1.0.1 (2021-02-27)

• [FIXED] A py.typed file is now bundled with the Arrow package to conform to PEP 561.

1.0.0 (2021-02-26)

After 8 years we're pleased to announce Arrow v1.0. Thanks to the entire Python community for helping make Arrow the amazing package it is today!

• [CHANGE] Arrow has dropped support for Python 2.7 and 3.5.
• [CHANGE] There are multiple breaking changes with this release, please see the migration guide <https://github.com/arrow-py/arrow/issues/832>_ for a complete overview.
• [CHANGE] Arrow is now following semantic versioning <https://semver.org/>_.
• [CHANGE] Made humanize granularity="auto" limits more accurate to reduce strange results.
• [NEW] Added support for Python 3.9.
• [NEW] Added a new keyword argument "exact" to span, span_range and interval methods. This makes timespans begin at the start time given and not extend beyond the end time given, for example:

.. code-block:: python

>>> start = Arrow(2021, 2, 5, 12, 30)
>>> end = Arrow(2021, 2, 5, 17, 15)
>>> for r in arrow.Arrow.span_range('hour', start, end, exact=True):
...     print(r)
...
(<Arrow [2021-02-05T12:30:00+00:00]>, <Arrow [2021-02-05T13:29:59.999999+00:00]>)
(<Arrow [2021-02-05T13:30:00+00:00]>, <Arrow [2021-02-05T14:29:59.999999+00:00]>)
(<Arrow [2021-02-05T14:30:00+00:00]>, <Arrow [2021-02-05T15:29:59.999999+00:00]>)
(<Arrow [2021-02-05T15:30:00+00:00]>, <Arrow [2021-02-05T16:29:59.999999+00:00]>)
(<Arrow [2021-02-05T16:30:00+00:00]>, <Arrow [2021-02-05T17:14:59.999999+00:00]>)

• [NEW] Arrow now natively supports PEP 484-style type annotations.
• [FIX] Fixed handling of maximum permitted timestamp on Windows systems.
• [FIX] Corrections to French, German, Japanese and Norwegian locales.
• [INTERNAL] Raise more appropriate errors when string parsing fails to match.

0.17.0 (2020-10-2)

... (truncated)

Commits

• ce69c31 Bump version to 1.0.3 and update CHANGELOG (#940)
• c577c76 Reconfigure arrow/init.py to avoid mypy --strict problems (#938)
• 77b4c5d Lower coverage requirement to 99% until humanize xfail tests are fixed (#937)
• 47c715d Swedish locale fix (#935)
• fc2cbaa Bump version to 1.0.2 and update CHANGELOG (#932)
• 86116ae Fix overflow on 32-bit Linux systems (#931)
• d66cb96 Remove timestamp property references in examples; replace with function where...
• 23800a8 Bump version to 1.0.1 and update CHANGELOG (#927)
• 7bc6784 Add py.typed export per PEP 561 (#925)
• 5248407 Bump version to 1.0.0 and update CHANGELOG (#924)
• 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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[majormajors]

This version requirement for arrow <1.0.0 means that the python-b2sdk package for Fedora 35 is currently broken and will not install since Fedora 35 ships with arrow 1.1.1. Installing b2sdk via pip on Fedora 35 is a workaround, but it would be nice to have the actual rpm fixed.

[mlech-reef]

@majormajors unfortunately because of some reasons that @ppolewicz can better explain, B2 SDK and B2 CLI are still supporting Python 3.5 so we had to pin our requirements to a few older packages, and arrow is one of them :/

[mlech-reef]

I would love to drop support for Python 3.5 as even Python 3.6 EOL is soon, but I don't know when it happen.

[majormajors]

Thanks for the insight. As I said, I can make it work by installing via pip for now, so it's not a big deal. I'll keep an eye out for future updates in case you find a way to bring it up to a newer version of arrow.

[sigmavirus24]

Can support for 3.5 look like keeping alive an old branch? 1.4.0 seems to support 3.5 with those older arrow versions. It's not fun, but I'd love to be able to make sure backblaze works on my machine again (Fedora 35) and help out with the upgrade

[sigmavirus24]

Alternatively, if there were a way to support 3.5 and arrow >= 1.0 then would that be accepted? It wouldn't be great for maintainability but it would make for happy users. Again, happy to assist with this

[ppolewicz]

@sigmavirus24 Python 3.6 is going EOL soon and we are looking into dropping support for 3.5 and 3.6. A soon as it expires (in about a month), no security fixes are going to be added etc, so it's not a safe thing to use anymore.

If you need to use b2cli on a very old machine, there is actually a self-contained binary build for it. As for b2-sdk-python, I think you should not be releasing new versions of your software with new features on a python version labeled as EOL. Our dependencies are dropping support for 3.5 and 3.6 too, so it's not just us.

As for Fedora 35, it's pretty new, uses python 3.9 or 3.10, so I don't think it should be a problem in your environment. Perhaps I don't understand your comment?

[sigmavirus24]

Fedora 35 ships with python3-b2sdk version 1.4.0 which asks for python3.10(arrow) >= 0.8 and python3.10(arrow) <1.0 but Fedora 35 ships only python3-arrow version 1.1. In other words if I

$ dnf install -y python3-b2sdk
Last metadata expiration check: 0:00:28 ago on Mon 22 Nov 2021 05:48:21 AM CST.
Error: 
 Problem: conflicting requests
  - nothing provides (python3.10dist(arrow) < 1 with python3.10dist(arrow) >= 0.8) needed by python3-b2sdk-1.4.0-3.fc35.noarch
(try to add '--skip-broken' to skip uninstallable packages)

And --skip-broken doesn't help for obvious reasons. Looking at your releases it seems like Fedora should be able to upgrade so I should be bothering the package maintainer instead.

[sigmavirus24]

Further, in attempting to understand why this constraint is in place, I can't find anywhere in b2sdk where we use Arrow.format. Is the problem on the Backblaze server-side or purely in the CLI? https://github.com/Backblaze/B2_Command_Line_Tool/blob/f466244c894fd385d71f95ae265bf29efbf7790b/b2/arg_parser.py#L96 I think it's possible to write logic in that function that would allow you to relax the upper constraint here before dropping support for 3.5 and 3.6 is my point

[sigmavirus24]

Backblaze/B2_Command_Line_Tool#769 is what I was referencing. I don't think it's ideal by any stretch of the imagination, but it should survive past the end of our lives.

[dependabot]

Looks like arrow is no longer updatable, so this is no longer needed.