python-colorama breaks jedi-vim plugin on xenial
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-colorama (Ubuntu) |
Fix Released
|
High
|
Barry Warsaw |
Bug Description
When the jedi-vim plugin runs colorama.init(), colorama assumes that the vim.message object which is sys.stdout (and/or sys.stderr) will have a 'closed' attribute. It doesn't which causes the following traceback:
Traceback (most recent call last):
File "/home/
import jedi_vim
File "/home/
import jedi
File "/home/
from jedi.api import Script, Interpreter, NotFoundError, set_debug_function
File "/home/
from jedi.parser import Parser, load_grammar
File "/home/
from jedi.parser import tree as pt
File "/home/
from jedi import cache
File "/home/
from jedi import debug
File "/home/
init()
File "/usr/lib/
wrap_
File "/usr/lib/
convert=
File "/usr/lib/
strip = conversion_
AttributeError: 'vim.message' object has no attribute 'closed'
This issue is described in more detail in https:/
Changed in python-colorama (Ubuntu): | |
status: | In Progress → Fix Released |
I uploaded 0.3.7-1 to Debian. As soon as Launchpad picks that up, I'll syncpackage it back to Ubuntu.