Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pylama global skip from pylama.ini doesn't skip #252

Open
magowiz opened this issue Mar 18, 2024 · 0 comments
Open

pylama global skip from pylama.ini doesn't skip #252

magowiz opened this issue Mar 18, 2024 · 0 comments

Comments

@magowiz
Copy link

magowiz commented Mar 18, 2024

Hi,
I'm trying to run pylama in mine cicd, the issue is that at some point in my workspace exists a venv in repository folder, probably created by other steps, the folder is .pyenv-usr-local-bin-python3.10 so I thought to setup a pylama.ini in order to skip that folder completely.

I wrote this:

[pylama]
format = pylint
skip = */.tox/*,*/.env/*,*/.pyenv-usr-local-bin-python3.10/*
linters = pylint,mccabe,mypy,eradicate,radon,vulture,pydocstyle,pycodestyle,pyflakes,isort

[pylama:pycodestyle]
max_line_length = 100

[pylama:pyflakes]
builtins = _

[pylama:mccabe]
complexity = 10

[pydocstyle]
convention = google

but for example pylint and isort for sure are still scanning that folder:

ERROR: /home/jenkins/workspace/zation_folder_travellint_develop/.pyenv-usr-local-bin-python3.10/lib/python3.10/site-packages/setuptools/_vendor/jaraco/functools.py Imports are incorrectly sorted and/or formatted.
pylint: Command line or configuration file:1: UserWarning: 'BaseException' is not a proper value for the 'overgeneral-exceptions' option. Use fully qualified name (maybe 'builtins.BaseException' ?) instead. This will cease to be checked at runtime when the configuration upgrader is released.
pylint: Command line or configuration file:1: UserWarning: 'Exception' is not a proper value for the 'overgeneral-exceptions' option. Use fully qualified name (maybe 'builtins.Exception' ?) instead. This will cease to be checked at runtime when the configuration upgrader is released.

Probably I misunderstood the way I should configure pylama to ignore completely folders.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant