* [PATCH] nvmetcli: Correct xrange usage for py3
@ 2020-04-01 19:13 Tony Asleson
2020-04-01 20:35 ` Sagi Grimberg
2020-04-03 6:55 ` Christoph Hellwig
0 siblings, 2 replies; 3+ messages in thread
From: Tony Asleson @ 2020-04-01 19:13 UTC (permalink / raw)
To: linux-nvme
If you are in a namespace and simply do a 'create' without specifying
a value you will get:
/subsystems/n...f8/namespaces> create
name 'xrange' is not defined
subsystems/n...f8/namespaces>
This is because xrange is not defined in python3 as python3 changed
it to range. As the code is already using six use six.move.xrange
which works for both python2 & python3.
Signed-off-by: Tony Asleson <tasleson@redhat.com>
---
nvmet/nvme.py | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/nvmet/nvme.py b/nvmet/nvme.py
index db8a03c..83fd75b 100644
--- a/nvmet/nvme.py
+++ b/nvmet/nvme.py
@@ -23,7 +23,7 @@ import stat
import uuid
import json
from glob import iglob as glob
-from six import iteritems
+from six import iteritems, moves
DEFAULT_SAVE_FILE = '/etc/nvmet/config.json'
@@ -556,7 +556,7 @@ class Namespace(CFSNode):
raise CFSError("Need NSID for lookup")
nsids = [n.nsid for n in subsystem.namespaces]
- for index in xrange(1, self.MAX_NSID + 1):
+ for index in moves.xrange(1, self.MAX_NSID + 1):
if index not in nsids:
nsid = index
break
@@ -816,7 +816,7 @@ class ANAGroup(CFSNode):
raise CFSError("Need grpid for lookup")
grpids = [n.grpid for n in port.ana_groups]
- for index in xrange(2, self.MAX_GRPID + 1):
+ for index in moves.xrange(2, self.MAX_GRPID + 1):
if index not in grpids:
grpid = index
break
--
2.25.1
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH] nvmetcli: Correct xrange usage for py3
2020-04-01 19:13 [PATCH] nvmetcli: Correct xrange usage for py3 Tony Asleson
@ 2020-04-01 20:35 ` Sagi Grimberg
2020-04-03 6:55 ` Christoph Hellwig
1 sibling, 0 replies; 3+ messages in thread
From: Sagi Grimberg @ 2020-04-01 20:35 UTC (permalink / raw)
To: Tony Asleson, linux-nvme
Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] nvmetcli: Correct xrange usage for py3
2020-04-01 19:13 [PATCH] nvmetcli: Correct xrange usage for py3 Tony Asleson
2020-04-01 20:35 ` Sagi Grimberg
@ 2020-04-03 6:55 ` Christoph Hellwig
1 sibling, 0 replies; 3+ messages in thread
From: Christoph Hellwig @ 2020-04-03 6:55 UTC (permalink / raw)
To: Tony Asleson; +Cc: linux-nvme
Thanks, applied.
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2020-04-03 6:55 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-04-01 19:13 [PATCH] nvmetcli: Correct xrange usage for py3 Tony Asleson
2020-04-01 20:35 ` Sagi Grimberg
2020-04-03 6:55 ` Christoph Hellwig
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox