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

Config file ignored in kwargs of legacy API #218

Closed
asottile opened this issue Apr 3, 2021 · 1 comment
Closed

Config file ignored in kwargs of legacy API #218

asottile opened this issue Apr 3, 2021 · 1 comment

Comments

@asottile
Copy link
Member

asottile commented Apr 3, 2021

In GitLab by @dhood on Jan 3, 2017, 19:00

Please describe the problem or feature

I am using the legacy API. My kwargs has a 'config' option with a config file. I find that the config file is not being used by flake8.

Currently [] is passed as the input to parse_configuration_and_cli in the legacy API get_style_guide here and then the kwargs options are applied afterwards. I think that applying the 'config' option after the call to parse_configuration_and_cli means that it is not used.


Please describe how you installed Flake8

$ pip3 install flake8

Using OS X 10.10.5.

Please provide the exact, unmodified output of flake8 --bug-report

$ flake8 --bug-report
{
  "dependencies": [
    {
      "dependency": "setuptools",
      "version": "19.4"
    }
  ],
  "platform": {
    "python_implementation": "CPython",
    "python_version": "3.5.1",
    "system": "Darwin"
  },
  "plugins": [
    {
      "plugin": "flake8-docstrings",
      "version": "1.0.2, pydocstyle: 1.0.0"
    },
    {
      "plugin": "import-order",
      "version": "0.11"
    },
    {
      "plugin": "mccabe",
      "version": "0.5.3"
    },
    {
      "plugin": "pycodestyle",
      "version": "2.2.0"
    },
    {
      "plugin": "pyflakes",
      "version": "1.3.0"
    }
  ],
  "version": "3.2.1"
}
@asottile
Copy link
Member Author

I'm planning to sunset the legacy api and provide a newer api which resolves this -- stay tuned in #140

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