#1178: changes to address datetime.utcnow deprecation warning #1182
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request Checklist
Thank you for taking the time to improve Arrow! Before submitting your pull request, please check all appropriate boxes:
tox
ormake test
to find out!).tox -e lint
ormake lint
to find out!).master
branch.If you have any questions about your code changes or any of the points above, please submit your questions along with the pull request and we will try our best to help!
Description of Changes
Python has raised deprecation warning for the use of
datetime.datetime.utcnow()
. The suggestion is to usedatetime.datetime.now(datetime.UTC)
or similar.This PR addresses just by swapping out all datetime utcnow() calls.
I don't think there's anything in documentation to be updated.
With the example raised in #1178 with
humanize()
:Python 3.12:
No more deprecation warning.
This also works with other python versions, like python 3.11:
One thing to note as I setup
virtualenv
for this:Despite being listed in requirements.txt,
python-dateutil
wasn't installed withmake build
. I had to manually install it.But that's a different thing to this PR.
Closes #1178