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
test_pytest_pylint.py tests failure with pylint 2.4.4 #105
Comments
seb128
added a commit
to seb128/pytest-pylint
that referenced
this issue
Dec 3, 2019
carsongee
added a commit
that referenced
this issue
Feb 10, 2020
carsongee
added a commit
that referenced
this issue
Feb 10, 2020
carsongee
added a commit
that referenced
this issue
Feb 10, 2020
carsongee
added a commit
that referenced
this issue
Feb 10, 2020
* Implemented option to output Pylint results to a reports file. (#100) * Implemented option to output Pylint results to a reports file. * Removed comment left in code. * Fixed string for Python 2.x support. * Fixed parameters differing in `PyLintItem.repr_failure` method. * Fixed file path in unit test. * Fixed unused argument `style` in `PylintItem.repr_failure`. * Fixed Python 2.7 Pylint error. * Improved `PyLintItem.runtest` function. * Disabling Pylint check due to Python 2 multiple inheritance differences. * Added support for newer docstring warning (#103) * Add support for Python 3.8 (#104) * Require Python 3.5+ (#106) This also bumps pytest's and pylint's minimal version to the first one with Python-3-only support. See also https://docs.pytest.org/en/latest/py27-py34-deprecation.html * Add ::PYLINT in pytest verbose mode (#101) * Dismiss a PytestUnknownMarkWarning * Add ::PYLINT in pytest verbose mode * Refactor and release notes (#109) * Removed passing pylint ignores (#111) Closes #105 Co-authored-by: José L. Patiño <jose.lpa@gmail.com> Co-authored-by: Michael <michael-k@users.noreply.github.com> Co-authored-by: Yan QiDong <yanqd0@outlook.com>
carsongee
added a commit
that referenced
this issue
Feb 10, 2020
* Release 0.15.0 (#110) * Implemented option to output Pylint results to a reports file. (#100) * Implemented option to output Pylint results to a reports file. * Removed comment left in code. * Fixed string for Python 2.x support. * Fixed parameters differing in `PyLintItem.repr_failure` method. * Fixed file path in unit test. * Fixed unused argument `style` in `PylintItem.repr_failure`. * Fixed Python 2.7 Pylint error. * Improved `PyLintItem.runtest` function. * Disabling Pylint check due to Python 2 multiple inheritance differences. * Added support for newer docstring warning (#103) * Add support for Python 3.8 (#104) * Require Python 3.5+ (#106) This also bumps pytest's and pylint's minimal version to the first one with Python-3-only support. See also https://docs.pytest.org/en/latest/py27-py34-deprecation.html * Add ::PYLINT in pytest verbose mode (#101) * Dismiss a PytestUnknownMarkWarning * Add ::PYLINT in pytest verbose mode * Refactor and release notes (#109) * Removed passing pylint ignores (#111) Closes #105 Co-authored-by: José L. Patiño <jose.lpa@gmail.com> Co-authored-by: Michael <michael-k@users.noreply.github.com> Co-authored-by: Yan QiDong <yanqd0@outlook.com> * Corrected pypi picky RST rendering Co-authored-by: José L. Patiño <jose.lpa@gmail.com> Co-authored-by: Michael <michael-k@users.noreply.github.com> Co-authored-by: Yan QiDong <yanqd0@outlook.com>
carsongee
added a commit
that referenced
this issue
Mar 18, 2020
* Release 0.15.0 (#110) * Implemented option to output Pylint results to a reports file. (#100) * Implemented option to output Pylint results to a reports file. * Removed comment left in code. * Fixed string for Python 2.x support. * Fixed parameters differing in `PyLintItem.repr_failure` method. * Fixed file path in unit test. * Fixed unused argument `style` in `PylintItem.repr_failure`. * Fixed Python 2.7 Pylint error. * Improved `PyLintItem.runtest` function. * Disabling Pylint check due to Python 2 multiple inheritance differences. * Added support for newer docstring warning (#103) * Add support for Python 3.8 (#104) * Require Python 3.5+ (#106) This also bumps pytest's and pylint's minimal version to the first one with Python-3-only support. See also https://docs.pytest.org/en/latest/py27-py34-deprecation.html * Add ::PYLINT in pytest verbose mode (#101) * Dismiss a PytestUnknownMarkWarning * Add ::PYLINT in pytest verbose mode * Refactor and release notes (#109) * Removed passing pylint ignores (#111) Closes #105 Co-authored-by: José L. Patiño <jose.lpa@gmail.com> Co-authored-by: Michael <michael-k@users.noreply.github.com> Co-authored-by: Yan QiDong <yanqd0@outlook.com> * Corrected pypi picky RST rendering * Corrected issue with disable mode (#115) Closes #114 Co-authored-by: José L. Patiño <jose.lpa@gmail.com> Co-authored-by: Michael <michael-k@users.noreply.github.com> Co-authored-by: Yan QiDong <yanqd0@outlook.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The build is failing with pylint 2.4.4 on Ubuntu
https://launchpadlibrarian.net/454058807/buildlog_ubuntu-focal-amd64.pytest-pylint_0.14.1-2_BUILDING.txt.gz
'-----------------------------------------------------------------
pytest_pylint.py PASSED [ 5%]
setup.py PASSED [ 11%]
test_pytest_pylint.py FAILED [ 17%]
=================================== FAILURES ===================================
________________________ [pylint] test_pytest_pylint.py ________________________
C:131, 4: Import outside toplevel (pytest_pylint) (import-outside-toplevel)
C:171, 4: Import outside toplevel (pytest_pylint) (import-outside-toplevel)
C:194, 4: Import outside toplevel (pytest_pylint) (import-outside-toplevel)
=============================== warnings summary ===============================
/usr/lib/python3/dist-packages/isort/pie_slice.py:362
/usr/lib/python3/dist-packages/isort/pie_slice.py:362: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated since Python 3.3, and in 3.9 it will stop working
class OrderedSet(collections.MutableSet):
-- Docs: https://docs.pytest.org/en/latest/warnings.html'
The text was updated successfully, but these errors were encountered: