public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Joseph Myers <jsm28@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] Fix deprecated utcnow() usage in build-many-glibcs.py
Date: Wed, 10 Jan 2024 13:02:37 +0000 (GMT)	[thread overview]
Message-ID: <20240110130237.453903858431@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=9da45337e4fcaa710e849e8c6baf22341c059e00

commit 9da45337e4fcaa710e849e8c6baf22341c059e00
Author: Joseph Myers <josmyers@redhat.com>
Date:   Wed Jan 10 13:02:16 2024 +0000

    Fix deprecated utcnow() usage in build-many-glibcs.py
    
    Running build-many-glibcs.py with Python 3.12 or later produces a
    warning:
    
    build-many-glibcs.py:566: 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).
      build_time = datetime.datetime.utcnow()
    
    Replace with datetime.datetime.now(datetime.timezone.utc) (the
    datetime.UTC constant is new in 3.11, so not suitable for use in this
    script at present).

Diff:
---
 scripts/build-many-glibcs.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/build-many-glibcs.py b/scripts/build-many-glibcs.py
index 9a929a6430..ec2ded6e56 100755
--- a/scripts/build-many-glibcs.py
+++ b/scripts/build-many-glibcs.py
@@ -563,7 +563,7 @@ class Context(object):
                 print(config.name, config.compiler.name)
             return
         self.clear_last_build_state(action)
-        build_time = datetime.datetime.utcnow()
+        build_time = datetime.datetime.now(datetime.timezone.utc)
         if action == 'host-libraries':
             build_components = ('gmp', 'mpfr', 'mpc')
             old_components = ()

                 reply	other threads:[~2024-01-10 13:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240110130237.453903858431@sourceware.org \
    --to=jsm28@sourceware.org \
    --cc=glibc-cvs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).