Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Boto3 UTC DeprecationWarnings #3889

Open
BookWorm0 opened this issue Oct 6, 2023 · 3 comments
Open

Boto3 UTC DeprecationWarnings #3889

BookWorm0 opened this issue Oct 6, 2023 · 3 comments
Labels
bug This issue is a confirmed bug. p2 This is a standard priority issue

Comments

@BookWorm0
Copy link

Describe the bug

Running the attached script under Python 3.12 with Python flag -Wa produces DepricationWarnings.
bug.txt

Expected Behavior

No warnings should be issued.

Current Behavior

For "import boto3", the warning is: dateutil\tz\tz.py:37: DeprecationWarning: datetime.datetime.utcfromtimestamp() is deprecated and scheduled for removal in a future version. Use timezone-aware objects to represent datetimes in UTC: datetime.datetime.fromtimestamp(timestamp, datetime.UTC).
EPOCH = datetime.datetime.utcfromtimestamp(0)

For s3client.list_objects, the warning is: botocore\auth.py:419: DeprecationWarning: datetime.datetime.utcnow() is deprecated and scheduled for removal in a future version. Use timezone-aware objects to represent datetimes in UTC: datetime.datetime.now(datetime.UTC).
datetime_now = datetime.datetime.utcnow()

Reproduction Steps

Rename the script from bug.txt to bug.py.

Run the script as follows from CMD.EXE:
py -Wa bug.py BUCKETNAME

where BUCKETNAME identifies an S3 bucket to which you are authorized to access.

Possible Solution

Boto source code should be modified as suggested in the warnings.

Additional Information/Context

No response

SDK version used

boto3-1.28.61 botocore-1.31.61

Environment details (OS name and version, etc.)

Windows 10 Pro Version 10.0.19045 Build 19045; Python 3.12.0

@BookWorm0 BookWorm0 added bug This issue is a confirmed bug. needs-triage This issue or PR still needs to be triaged. labels Oct 6, 2023
@tim-finnigan
Copy link
Contributor

Hi @BookWorm0 thanks for reaching out. The team is aware of this issue and working on addressing the warnings. These deprecations won't cause impact currently beyond the warnings. The required changes are not fully backwards compatible for existing usage. We'll be prioritizing a more robust fix in an upcoming release.

@kfrydel
Copy link

kfrydel commented Oct 16, 2023

@tim-finnigan Thank you very much!

@StevenMapes
Copy link

Any update on this as the warnings break my CI/CD flow unless I turn off error::DeprecationWarning which I really don't want to

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a confirmed bug. p2 This is a standard priority issue
Projects
None yet
Development

No branches or pull requests

4 participants