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
avoid deprecated utcfromtimestamp #1285
Conversation
oh dear, CI is not looking healthy |
Yeah that's always the problem with this project (and most of the other low-velocity projects I have). Every time I try to make a change the CI has broken out from under me and I have to spend the time I had budgeted to make the change on fixing the CI. |
Thanks! |
## What do these changes do? Ignore `dateutil` DeprecationWarning on Python 3.12. It's already fixed on upstream dateutil/dateutil#1285. Just waiting for a new release now. Requires #7503 --------- Co-authored-by: Sam Bull <git@sambull.org> Co-authored-by: Sam Bull <aa6bs0@sambull.org>
## What do these changes do? Ignore `dateutil` DeprecationWarning on Python 3.12. It's already fixed on upstream dateutil/dateutil#1285. Just waiting for a new release now. Requires #7503 --------- Co-authored-by: Sam Bull <git@sambull.org> Co-authored-by: Sam Bull <aa6bs0@sambull.org> (cherry picked from commit 40203b7)
…[3.12] (#7506) **This is a backport of PR #7505 as merged into master (40203b7).** ## What do these changes do? Ignore `dateutil` DeprecationWarning on Python 3.12. It's already fixed on upstream dateutil/dateutil#1285. Just waiting for a new release now. Requires #7503 Co-authored-by: Marc Mueller <30130371+cdce8p@users.noreply.github.com>
@pganssle Can you push a release with this change to PyPI please? |
I think the merged solution may be wrong. I think it should keep timezone-aware object, something like this: EPOCH = datetime.datetime.fromtimestamp(0, datetime.UTC) Edit: |
Fixes #1284