From: Andreas Florath <xen@flonatel.org>
To: Isaku Yamahata <yamahata@valinux.co.jp>
Cc: kuwa@jp.fujitsu.com, xen-devel@lists.xensource.com
Subject: Re: [PATCH] python: make tools/python/xen/util/fileuri.py work on python 2.3
Date: Sun, 26 Jul 2009 23:07:29 +0200 [thread overview]
Message-ID: <4A6CC591.9050606@flonatel.org> (raw)
In-Reply-To: <20090723040408.GM6393%yamahata@valinux.co.jp>
Hello!
It would be nice, if you can please provide some more information:
especially the OS / Distribution (Version) you are using. I looked
around but did not find any Linux distribution nowadays which still
comes with python2.3 - even Debian etch (which is known to be 'stable'
:-) ) comes with python 2.4.4.
Looking though the xen-unstable tree I found at least two different
supported python version numbers:
1. 'README' : ... Development install of Python v2.3 or later...
2. './docs/src/user.tex': ... Development installation of Python v2.2
or later ...
Are there any guidelines (written or unwritten) which python version to
support for new patches?
IMHO at least 2.4, 2.5 and 2.6 should be supported.
When interpreting the documentation literally also python 3 should work.
Must 2.3 and maybe even 2.2 be supported?
Is there some kind of roadmap saying e.g.: xen 3.6 will be the last
version which supports python 2.3? Or: starting from xen 4.0 python 3
will be supported?
Background:
The feature was removed from the repository because of another bug
report. But before providing a corrected version, I want to be sure
that I'll get all aspects of the changes send in the meantime;
especially here to test the feature with all supported python versions.
Kind regards
Andreas Florath
next prev parent reply other threads:[~2009-07-26 21:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-23 4:04 [PATCH] python: make tools/python/xen/util/fileuri.py work on python 2.3 Isaku Yamahata
2009-07-26 21:07 ` Andreas Florath [this message]
2009-07-27 3:02 ` Isaku Yamahata
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=4A6CC591.9050606@flonatel.org \
--to=xen@flonatel.org \
--cc=kuwa@jp.fujitsu.com \
--cc=xen-devel@lists.xensource.com \
--cc=yamahata@valinux.co.jp \
/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.