vronp: You appear to be running into a configuration issue with Xen; I'm fairly confident that it's unrelated to this bug.
I've managed to reproduce this on Jaunty. It looks like the exception you're seeing is actually being raised in an exception handling clause, so it's squashing the actual error. If you just try to run `import curses; stdscr=curses.initscr()` in a Python 2.5 shell, you get:
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/usr/lib/python2.5/curses/__init__.py", line 30, in initscr
setupterm(term=_os.environ.get("TERM", "unknown"),
NameError: global name '_os' is not defined
This appears to be a bug in the python2.5 packaging, and not in Xen. Specifically, the patch debian/patches/curses-init.dpatch is incomplete.
vronp: You appear to be running into a configuration issue with Xen; I'm fairly confident that it's unrelated to this bug.
I've managed to reproduce this on Jaunty. It looks like the exception you're seeing is actually being raised in an exception handling clause, so it's squashing the actual error. If you just try to run `import curses; stdscr= curses. initscr( )` in a Python 2.5 shell, you get:
Traceback (most recent call last): python2. 5/curses/ __init_ _.py", line 30, in initscr term=_os. environ. get("TERM" , "unknown"),
File "<stdin>", line 1, in <module>
File "/usr/lib/
setupterm(
NameError: global name '_os' is not defined
This appears to be a bug in the python2.5 packaging, and not in Xen. Specifically, the patch debian/ patches/ curses- init.dpatch is incomplete.