Re: [Xen-devel] Problem with xm in xen-unstable

[Mark Williamson <mark.williamson@xxxxxxxxxxxx>]

It's probably a Python version issue: FutureWarning appeared in Python 2.3 - 
are you using something earlier.

The alternate fix it to just comment out that line of the code - in normal use 
it shouldn't matter ;-)

Cheers,
Mark

On Monday 16 May 2005 21:52, Santos, Jose Renato G wrote:
>   Hi,
>
>   I got xenoprof ported to xen-unstable and I am trying
>   to test it on the latest unstable version, but
>   I am having problems running the xm tool.
>   I am using the xen-unstable-src.tgz tar ball from last night
>   and I am having the following error. Not sure if there
>   is some piece of the old version of xen still around
>   that may be causing this or if xm is currently broken in
>   unstable? Anyone has an idea of what could be wrong?
>   Thanks
>
>   Renato
>
> ==================================================================
> # xm help
> Traceback (most recent call last):
>   File "/usr/sbin/xm", line 8, in ?
>     from xen.xm import main
>   File "/usr/lib/python/xen/xm/main.py", line 10, in ?
>     warnings.filterwarnings('ignore', category=FutureWarning)
> NameError: name 'FutureWarning' is not defined
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel