From: John Kacur <jkacur@redhat.com>
To: linux-rt-users <linux-rt-users@vger.kernel.org>
Cc: Clark Williams <williams@redhat.com>, John Kacur <jkacur@redhat.com>
Subject: [PATCH 1/4] python-linux-procfs: Remove import of range from six.moves
Date: Thu, 9 Oct 2025 16:27:29 -0400 [thread overview]
Message-ID: <20251009202732.57880-1-jkacur@redhat.com> (raw)
We're fully python3, remove import of range and just use the python3
built-in
Signed-off-by: John Kacur <jkacur@redhat.com>
---
procfs/procfs.py | 2 --
procfs/utilist.py | 3 ---
2 files changed, 5 deletions(-)
diff --git a/procfs/procfs.py b/procfs/procfs.py
index 7cc7371b53e2..e3f9f44614ef 100755
--- a/procfs/procfs.py
+++ b/procfs/procfs.py
@@ -11,12 +11,10 @@ import platform
import re
import time
from functools import reduce
-from six.moves import range
from procfs.utilist import bitmasklist
VERSION = "0.7.3"
-
def is_s390():
""" Return True if running on s390 or s390x """
machine = platform.machine()
diff --git a/procfs/utilist.py b/procfs/utilist.py
index e6314f0fd89c..e36c739862a4 100755
--- a/procfs/utilist.py
+++ b/procfs/utilist.py
@@ -6,9 +6,6 @@
# Copyright (C) 2007 Red Hat, Inc.
#
-from six.moves import range
-
-
def hexbitmask(l, nr_entries):
hexbitmask = []
bit = 0
--
2.51.0
next reply other threads:[~2025-10-09 20:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 20:27 John Kacur [this message]
2025-10-09 20:27 ` [PATCH 2/4] python-linux-procfs: Modernize packaging and update authorship John Kacur
2025-10-09 20:27 ` [PATCH 3/4] python-linux-procfs: Fix spelling mistakes in comments John Kacur
2025-10-09 20:27 ` [PATCH 4/4] python-linux-procfs: Bump version to 0.7.4 John Kacur
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=20251009202732.57880-1-jkacur@redhat.com \
--to=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=williams@redhat.com \
/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 NNTP newsgroup(s).