Error: Message already defined #221

Closed
barraponto opened this Issue May 13, 2013 · 2 comments

Projects

None yet

2 participants

@barraponto

Recently, I've started seeing the following error everytime I save the file (which, I think, triggers pylint):

ERROR:root:Traceback (most recent call last):
  File "/home/barraponto/.spf13-vim-3/.vim/bundle/python-mode/pylibs/pylama/main.py", line 48, in run
    result = linter(path, code=code, **meta)
  File "/home/barraponto/.spf13-vim-3/.vim/bundle/python-mode/pylibs/pylama/utils.py", line 107, in pylint
    [path] + attrs, reporter=Reporter(), exit=False)
  File "/home/barraponto/.spf13-vim-3/.vim/bundle/python-mode/pylibs/pylama/pylint/lint.py", line 925, in __init__
    linter.load_default_plugins()
  File "/home/barraponto/.spf13-vim-3/.vim/bundle/python-mode/pylibs/pylama/pylint/lint.py", line 331, in load_default_plugins
    checkers.initialize(self)
  File "/home/barraponto/.spf13-vim-3/.vim/bundle/python-mode/pylibs/pylama/pylint/checkers/__init__.py", line 137, in initialize
    package_load(linter, __path__[0])
  File "/home/barraponto/.spf13-vim-3/.vim/bundle/python-mode/pylibs/pylama/pylint/checkers/__init__.py", line 160, in package_load
    module.register(linter)
  File "/home/barraponto/.spf13-vim-3/.vim/bundle/python-mode/pylibs/pylama/pylint/checkers/string_format.py", line 163, in register
  File "/home/barraponto/.spf13-vim-3/.vim/bundle/python-mode/pylibs/pylama/pylint/lint.py", line 406, in register_checker
    self.register_messages(checker)
  File "/home/barraponto/.spf13-vim-3/.vim/bundle/python-mode/pylibs/pylama/pylint/utils.py", line 157, in register_messages
    'Message symbol %r is already defined' % msgsymbol
AssertionError: Message symbol 'missing-format-string-key' is already defined

I'm using spf13-vim, console vim (built with graphic support and batteries included) and archlinux (which has python3 by default, fwiw).

@klen
Collaborator
klen commented May 14, 2013

Drop all "*.pyc" files from python-mode directory.

@klen klen closed this May 14, 2013
@barraponto

Thanks, the fix worked pretty fine. If it is a known issue, can we have instructions on the error message? Maybe automatic cleanup of pyc files?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment