pylint-plugin-utils

This project publishes no release notes. Between 0.8.2 and 0.9.0 there were 12 commits, 5 of them substantive:

• Bumping lock file to get newer versions
• Updating pre-commit
• Updating dependencies, dropping Python<3.9 and fixing workflows
• Updating default python version to match project constrints
• Removing coveralls as it causes version constraint issues and there is only one test anyway

This project publishes no release notes. Between 0.8 and 0.8.2 there were 2 commits, 2 of them substantive:

• Fixing up packaging - moved to poetry but forgot classifiers, and got license specification wrong
• [#29] Removing the LICENSE and README files from the project include section, as this had unintended consequences of installing them into the site-packages directory instead of along side the package code. This is related to https://github.com/python-poetry/poetry/issues/2015 . Since the LICENSE is available in the dist-info directory along side the package, then this is sufficient.

This project publishes no release notes. Between 0.7 and 0.8 there were 8 commits, 6 of them substantive:

• triggering a build to try to trigger pre-commit.ci
• Converting to poetry for packaging instead of legacy setup.py method
• Bit of faff to get isort and pre-commit working happily, also flake8 seemed to die with that config file, and flake8 now appears to have no issues with the code here
• Bit of a janky fix to tests here - pylint 2.13 seems to have introduced something to the linter which cannot be pickled, which causes the tests to fail. However, the tests were to ensure that the additions of pylint-plugin-utils did not break picklability. So for now, for tests, just ignore the fact that the linter will not pickle because it is not the fault of pylint-plugin-utils...
• Fixing #26 by abandoning the test which is very very out of date and unecessary now
• Updating CI config with poetry packaging

This project publishes no release notes. Between 0.6 and 0.7 there were 19 commits, 16 of them substantive:

• 20 - Replaced closure+function to keep state with classes implementing call
• 20 - Added pre-commit + fixing all black and isort issues
• 20 - Removing unsed code
• 20 - Added all supported python versions under travis.yaml and changed the coverage command to pytest-cov
• 20 - Github Actions inspired (copied) from pylint project
• 20 - Trying to trigger github actions
• Creating dummy CI to enable actions
• 20 - Removing pylint hook from ci
• 20 - Added coveralls dedependency
• 20 - Changed build badge to point to github actions and removed code health badge
• 20 - Added black style badge
• 20 - Removed travis.yml file
• Bumping version for release
• 22 - Removed ci.yml files as it is a dummy workflow
• #22 - Fixing build badge
• Removed small formatting error (#22)

This project publishes no release notes. Between 0.4 and 0.6 there were 13 commits, 10 of them substantive:

• Expand test matrix
• [FIX] add support for pylint 2.3.0 (https://github.com/PyCQA/pylint/commit/da67a9da682e51844fbc674229ff6619eb9c816a)
• [FIX] Support MessagesStore.get_message_definitions interface.
• Using python 3.7 too as well as testing multiple pylint versions
• Bumping version for release h
• Dropping support for old versions of things
• Import exception from pylint.exceptions instead of utils
• Cleanup import and drop support for pylint < 1.7
• Add minimal required version of pylint to setup.py
• Bumping version for new release

This project publishes no release notes. Between 0.2.4 and 0.4 there were 28 commits, 20 of them substantive:

• Bumping development version
• MANIFEST.in: Include the license file.
• Adding PYthon 3.5 and 3.6 to build matrix
• --use-mirrors no longer exists
• pypin.in seens to have died and the badges are not useful anyway really
• Fixing old badge markup
• Updating setup.py for impending new (very minor) release
• Actually running coveralls
• Oops, remembered why this did not submit coverage information now...
• Merging in changes from develop branch, made a mess of merging in a PR
• Made a mess by releasing from the wrong branch so version 0.2.5 is no longer on Pypi...
• Just use setuptools.
• Don't explicitly depend on astroid
• Add simple test
• Update links to point to PyCQA after migration
• Bumping version after some additional PRs
• Ditching Py2 due to pylint having done the same
• Fix compatibility with Pylint 2.0
• Bumping release version to 0.4 to include recent pylint v2.0 compatability additions
• Changing classifiers to be list rather than tuble to avoid upload errors

This project publishes no release notes. Between 0.2.3 and 0.2.4 there were 3 commits, 2 of them substantive:

• [REF] init: Compatibility with future pylint 2.0
• Bumping version for hotfix release

This project publishes no release notes. Between 0.2.2 and 0.2.3 there were 5 commits, 5 of them substantive:

• Bumping dev version
• Merging branch master into develop
• Merging from master
• Pylint 1.4+ changed the add_message API, so here is a nasty hack to figure out which is being used.
• Bumping version for hotfix