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

Released 0.19.0 #172

Merged
merged 30 commits into from
Sep 10, 2022
Merged

Released 0.19.0 #172

merged 30 commits into from
Sep 10, 2022

Conversation

carsongee
Copy link
Owner

@carsongee carsongee commented Sep 10, 2022

Release time! Thanks to all the amazing contributors 👏 👏 👏

carsongee and others added 29 commits November 9, 2020 00:37
Due to the resulting in potential false passes
Added black and isort and fixed pytest dev branch
Changes the way that the config file is retrieved from pylint.config. Previously
this was done using the static `variable pylint.config.PYLINTRC` which is defined
at load by iterating over all the files found via
`pylint.config.find_default_config_files()` until one ending in "pylintrc" is
found. In pylint itself config seems instead to be found by calling
`next(find_default_config_files(), None)` which is also able to find setup.cfg or
pyproject.toml based config files automatically. I have thus changed PyLintPlugin
to use the same version and can now call `py.test --pylint` and have config from
my pyproject.toml picked up correctly.

I have added one additional test, essentially copying the existing
`test_pylint_file_toml`, but now called `test_pyline_file_pyproject_toml`, which
is modified to name the config file `pyproject.toml` and does not pass the
`--pyline-fcfile` option but expects it to be auto-detected. This test passes
when the file is called pyproject.toml but fails when it is called something
different.
…is being

used and there is no support for pyproject.toml etc.
… file but

still ran the test that would fail when it couldn't detect the file. this
should fix that. I also had to modify the test invalidate_cache_when_config_changes
as autofinding the config caused that test to fail (which I assume was not
intended)
…figured,

not at load time of the module which may have been affecting things. Also
made a change to the import of pylint.config to comply with isort and
pylint 2.3
feat: auto-find config that is not pylintrc based
Python 3.5 reached its EOL in September 2020[1] and
Python 3.6 reached its EOL in December 2021.

[1]: https://peps.python.org/pep-0478/
[2]: https://peps.python.org/pep-0494/
pytest-flake8 doesn't work with flake8 v5.  There's no need to run
black, flake8, and isort with every combination of pylint and pytest.
- Consider using 'with' for resource-allocating operations (consider-using-with)
- Using open without explicitly specifying an encoding (unspecified-encoding)
- Formatting a regular string which could be a f-string (consider-using-f-string)
@carsongee carsongee merged commit 0c83291 into release Sep 10, 2022
@carsongee carsongee deleted the rc/0.19.0 branch September 10, 2022 21:29
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

Successfully merging this pull request may close these issues.

4 participants