You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This probably happened to you because there is a clash with packages that python mode imports, basically there is another pylama on sys.path that can be imported and it takes precedence. It could happen because you did pip install and then uninstall and some dangling python libraries are left behind. Or perhaps something is installed it into global scope?
I have a very similar issue to yours, when I install (by accident or not) setuptools, it leaves me with pkg_resources installed on my PC that actually pylama tries to import from and because this lib is not updated for quite some time, import fails with message:
ImportError: cannot import name 'iter_entry_points' from 'pkg_resources' (unknown location)
And this is what pip told me when I uninstalled setuptools:
Found existing installation: setuptools 67.0.0
Uninstalling setuptools-67.0.0:
Would remove:
~/Envs/some_env/lib/python3.9/site-packages/_distutils_hack/*
~/Envs/some_env/lib/python3.9/site-packages/distutils-precedence.pth
~/Envs/some_env/lib/python3.9/site-packages/pkg_resources/*
~/Envs/some_env/lib/python3.9/site-packages/setuptools-67.0.0.dist-info/*
~/Envs/some_env/lib/python3.9/site-packages/setuptools/*
Would not remove (might be manually added):
~/Envs/some_env/lib/python3.9/site-packages/pkg_resources/_vendor/appdirs.py
~/Envs/some_env/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/_compat.py
~/Envs/some_env/lib/python3.9/site-packages/pkg_resources/_vendor/pyparsing.py
~/Envs/some_env/lib/python3.9/site-packages/pkg_resources/_vendor/six.py
~/Envs/some_env/lib/python3.9/site-packages/pkg_resources/py31compat.py
Proceed (y/n)? y
Open any python file with your it will complain about sys.exit but will display path to your pylama
Messages maintainer: Mike Williams <mrw@eandem.co.uk>
"app.py" 84L, 2899C
pylama path: ['$HOME/Projects/setup/.vim/plugged/python-mode/pymode/libs/pylama']
Error detected while processing $HOME/Projects/setup/.vim/plugged/python-mode/autoload/pymode/lint.vim:
line 1:
E880: Can't handle SystemExit of python exception in vim
If message is too fast for you just do :message in vim to display all errors that occurred so far.
Activity
diraol commentedon May 7, 2022
You probably have issues with your installation, Probably you haven't cloned the git submodules we have in the repo.
Please, follow the Installation instructions from our readme.
smilesun commentedon Oct 7, 2022
I have the same problem even if I run git submodule
or delte the directory and reinstall via
git clone --recurse-submodules https://github.com/python-mode/python-mode.gitsmilesun commentedon Oct 7, 2022
smilesun commentedon Dec 21, 2022
@diraol , any update?
Drachenfels commentedon Feb 17, 2023
It's obsolete pylama submodule, extensions.py was removed in pylama in November 24th 2021 with this commit: klen/pylama@c7d4abe#diff-79ada95cf7608fbd1a0d29bc0fe0467460ff13abdf10c4b22ae3fb738553d410
This probably happened to you because there is a clash with packages that python mode imports, basically there is another pylama on sys.path that can be imported and it takes precedence. It could happen because you did pip install and then uninstall and some dangling python libraries are left behind. Or perhaps something is installed it into global scope?
I have a very similar issue to yours, when I install (by accident or not) setuptools, it leaves me with pkg_resources installed on my PC that actually pylama tries to import from and because this lib is not updated for quite some time, import fails with message:
And this is what pip told me when I uninstalled setuptools:
Drachenfels commentedon Feb 17, 2023
A hint how to figure out the problem:
If message is too fast for you just do
:messagein vim to display all errors that occurred so far.