From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Javi Merino <javi.merino@cloud.com>
Cc: xen-devel@lists.xenproject.org, Wei Liu <wl@xen.org>,
Anthony PERARD <anthony.perard@citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: [XEN PATCH v1] tools/python: Add python3 compatibility
Date: Tue, 10 Oct 2023 17:27:03 +0200 [thread overview]
Message-ID: <ZSVtR1ct4Hik4XM8@mail-itl> (raw)
In-Reply-To: <efb10e537e37df1995dd8f87c28a8eb64ec9b61e.1696947009.git.javi.merino@cloud.com>
[-- Attachment #1: Type: text/plain, Size: 1877 bytes --]
On Tue, Oct 10, 2023 at 03:18:45PM +0100, Javi Merino wrote:
> Most of the work for python3 compatibility was done in
> 1430c5a8cad4 (tools/python: Python 3 compatibility, 2019-12-18). This
> just adds a few builtins needed for python3.
>
> Resolves: xen-project/xen#156
>
> Signed-off-by: Javi Merino <javi.merino@cloud.com>
> ---
>
> I haven't tested it.
>
> README | 1 +
> tools/python/scripts/convert-legacy-stream | 3 +++
> 2 files changed, 4 insertions(+)
>
> diff --git a/README b/README
> index 855db01d36..44ed88c392 100644
> --- a/README
> +++ b/README
> @@ -51,6 +51,7 @@ provided by your OS distributor:
> * POSIX compatible awk
> * Development install of zlib (e.g., zlib-dev)
> * Development install of Python 2.7 or later (e.g., python-dev)
> + - If using Python 2.7, you also need the future module. This is not needed for Python 3.
> * Development install of curses (e.g., libncurses-dev)
> * Development install of openssl (e.g., openssl-dev)
> * Development install of x11 (e.g. xorg-x11-dev)
> diff --git a/tools/python/scripts/convert-legacy-stream b/tools/python/scripts/convert-legacy-stream
> index 7fe375a668..26a66c50fc 100755
> --- a/tools/python/scripts/convert-legacy-stream
> +++ b/tools/python/scripts/convert-legacy-stream
> @@ -8,6 +8,9 @@ Convert a legacy migration stream to a v2 stream.
> from __future__ import print_function
> from __future__ import division
>
> +from builtins import zip
> +from builtins import range
> +from builtins import object
In which python version it's needed? The thing about builtins is they
are available without explicit import.
> import sys
> import os, os.path
> import syslog
> --
> 2.42.0
>
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-10-10 15:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 14:18 [XEN PATCH v1] tools/python: Add python3 compatibility Javi Merino
2023-10-10 15:27 ` Marek Marczykowski-Górecki [this message]
2023-10-12 12:54 ` Javi Merino
2023-10-10 16:34 ` Andrew Cooper
2023-10-12 13:04 ` Javi Merino
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=ZSVtR1ct4Hik4XM8@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=javi.merino@cloud.com \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.