public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Florian Weimer <fw@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc] scripts/glibcelf.py: Mark as UNSUPPORTED on Python 3.5 and earlier Date: Mon, 25 Apr 2022 07:15:12 +0000 (GMT) [thread overview] Message-ID: <20220425071512.84702385734F@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=b571f3adffdcbed23f35ea39b0ca43809dbb4f5b commit b571f3adffdcbed23f35ea39b0ca43809dbb4f5b Author: Florian Weimer <fweimer@redhat.com> Date: Fri Apr 22 19:34:52 2022 +0200 scripts/glibcelf.py: Mark as UNSUPPORTED on Python 3.5 and earlier enum.IntFlag and enum.EnumMeta._missing_ support are not part of earlier Python versions. Diff: --- scripts/glibcelf.py | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/scripts/glibcelf.py b/scripts/glibcelf.py index 8f7d0ca184..da0d5380f3 100644 --- a/scripts/glibcelf.py +++ b/scripts/glibcelf.py @@ -28,6 +28,12 @@ import collections import enum import struct +if not hasattr(enum, 'IntFlag'): + import sys + sys.stdout.write( + 'warning: glibcelf.py needs Python 3.6 for enum support\n') + sys.exit(77) + class _OpenIntEnum(enum.IntEnum): """Integer enumeration that supports arbitrary int values.""" @classmethod
reply other threads:[~2022-04-25 7:15 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=20220425071512.84702385734F@sourceware.org \ --to=fw@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: linkBe 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).