From: Matthias Klose <doko@debian.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen@packages.debian.org, xen-devel@lists.xensource.com
Subject: Re: [Pkg-xen-devel] using xen tools with python2.6
Date: Mon, 13 Sep 2010 10:57:47 +0200 [thread overview]
Message-ID: <4C8DE78B.10709@debian.org> (raw)
In-Reply-To: <1284367127.14311.14256.camel@zakaz.uk.xensource.com>
On 13.09.2010 10:38, Ian Campbell wrote:
> On Sun, 2010-09-12 at 16:25 +0200, Matthias Klose wrote:
>> there are at least some syntax errors when trying to use the xen utils with
>> python2.6. The attached patch changes these string exception into ValueError's.
>
> Thanks Matthias.
>
>> - tools/python/xen/util/bugtool.py (getBugTitle)
>> - tools/python/xen/xend (class XendBase): not catched
>> - tools/python/xen/xm/xenapi_create.py (sxp2xmlconvert_sxp_to_xml):
>> the method already raises a ValueError for similiar condition.
>> - tools/python/xen/xm/main.py (xm_network_attach): not catched.
>>
>> For all but maybe the first one, the replacement of the string exceptions into
>> ValueError's seems to be safe.
>
> Why is the first one potentially unsafe?
because I didn't check where it's used.
> What do you mean by "not catched" here? Just that nothing catches the
> exception?
yes, and the first one seems to match this definition too.
> Please could you provide a Signed-off-by line for upstream?
hmm, any pointers? I hope my friendly distribution packager could help ...
Matthias
next prev parent reply other threads:[~2010-09-13 8:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-12 14:25 using xen tools with python2.6 Matthias Klose
2010-09-13 8:38 ` [Pkg-xen-devel] " Ian Campbell
2010-09-13 8:57 ` Matthias Klose [this message]
2010-09-13 9:14 ` Ian Campbell
2010-09-14 15:55 ` Matthias Klose
[not found] ` <m2n.s.1OvAmk-0012nR@chiark.greenend.org.uk>
2010-09-14 16:46 ` Ian Jackson
2010-09-15 8:38 ` Ian Campbell
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=4C8DE78B.10709@debian.org \
--to=doko@debian.org \
--cc=Ian.Campbell@citrix.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen@packages.debian.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 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).