Unpin python-dateutil

[flying-sheep]

Description

Unpins a restrictive upper dependency bound

Related Issue

Fixes #313

Motivation and Context

Since there‘s no explanation why your python-dateutil requirement is pinned, I’m going to assume it’s no longer an issue.

Upper bounds are bad if not absolutely necessary: https://iscinumpy.dev/post/bound-version-constraints/

How Has This Been Tested?

I’m going to rely on your CI

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• N/A I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• N/A I have added tests to cover my changes.
• All new and existing tests passed.

[rabbittsoup]

I would think a dateutil requirement should remain in requirements in some form if gimme-aws-creds uses dateutil somewhere. Just not pinned as restrictively.

[rabbittsoup]

Interesting, a quick search for dateutil doesn’t seem to show it being used in the code at all. If that’s true, then, yeah, it should be removed.

[alexlatchford]

Thanks @flying-sheep for the PR, any chance you could push out a release with this change @bwynsm? We currently have some other dependencies (notably jupyter-client) backpinned because of this change so hoping to clear this up if possible!