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

Update pylint to 3.3.0 #813

Closed
wants to merge 1 commit into from
Closed

Conversation

pyup-bot
Copy link
Collaborator

This PR updates pylint from 2.1.1 to 3.3.0.

Changelog

2.6.0

-------------

NOTICE
~~~~~~

This version drops support for Python 3.7 - latest Pylint no longer supports 3.7, and CI tasks were taking hours under 3.7. `Python 3.7 <https://www.python.org/downloads/release/python-3717/>`_  received its last security update more than a year ago (from the date of this release).

Bugfixes
~~~~~~~~

- Added Django aliases for ranges to support psycopg 2 and 3 (`421 <https://github.com/pylint-dev/pylint-django/pull/421>`_)
- Support for PYthon 3.12 datetime (`427 <https://github.com/pylint-dev/pylint-django/pull/427>`_)
- Fixed location of installed LICENSE file (`431 <https://github.com/pylint-dev/pylint-django/issues/431>`_)
- Fixed ForeignKeyStringChecker referencing linter config incorrectly (`430 <https://github.com/pylint-dev/pylint-django/issues/430>`_)

2.5.5

---------------------------

NOTICE
~~~~~~

This version drops support for Python 3.6

Bugfixes
~~~~~~~~

- Fixed compatibility issue with datetime classes and python `3.12` (`425 <https://github.com/pylint-dev/pylint-django/issues/425>`_)

2.5.3

---------------------------

Bugfixes
~~~~~~~~

- Fixed compatibility issue between pylint `2.12` and `2.13` to construct `ScopeConsumer` tuples correctly depending on version (`358 <https://github.com/PyCQA/pylint-django/issues/358>`_)

Other
~~~~~

- pylint version is now pinned to `<3` to give breathing space to update pylint-django before the major update lands

2.5.2

---------------------------

Bugfixes
~~~~~~~~

- Fixed crash with assigning a class to a variable, and referencing the variable when subclassing (`349 <https://github.com/PyCQA/pylint-django/issues/349>`_)

Other
~~~~~

- CI now tests against Django 4.0

2.5.1

---------------------------

Bugfixes
~~~~~~~~

- Fixed pickling for `augment_visit` (`276 <https://github.com/PyCQA/pylint-django/issues/276>`_)

2.5.0

---------------------------

Bugfixes
~~~~~~~~

- Fixed compatibility with astroid 2.9.1 (`343 <https://github.com/PyCQA/pylint-django/issues/343>`_)

New
~~~

- Removed false positive error of missing member in TextChoices tuples `298 <https://github.com/PyCQA/pylint-django/issues/298>`_ (see pulls `#330 <https://github.com/PyCQA/pylint-django/pull/330>`_ and `#345 <https://github.com/PyCQA/pylint-django/pull/345>`_)
- Moved from Travis CI to GitHub Actions (`366 <https://github.com/PyCQA/pylint-django/pull/366>`_ and `#340 <https://github.com/PyCQA/pylint-django/pull/340>`_)
- Added pre-commit configuration and began enforcing black/isort code formatting
- Multiple test fixes (including `338 <https://github.com/PyCQA/pylint-django/issues/338>`_) - newer versions of pylint expect a different format for the expected messages txt files.
- Bumped dependency for pylint-django-utils to get `multi-threaded pylint support <https://github.com/PyCQA/pylint-plugin-utils/pull/21>`_

2.4.4

---------------------------

- Fix compatibility issues with pylint >= 2.8. Fixes
`322 <https://github.com/PyCQA/pylint-django/issues/322>`_ and
`323 <https://github.com/PyCQA/pylint-django/issues/323>`_

2.4.3

---------------------------

- Start testing with Django 3.2 on Python 3.9 (Michael K.)
- Teach pylint-django about all HTTP methods from the View class, not only
``get`` and ``post`` (Nicolás Quiroz)
- Typo fixes for
`314 <https://github.com/PyCQA/pylint-django/issues/314>`_ (John Sandall)
- Ignore ``unused-argument`` for ``*args``, ``**kwards`` in view method signatures

2.4.2

---------------------------

- Moved `Faker` dependencies to test-only `304 <https://github.com/PyCQA/pylint-django/issues/304>`_

2.4.1

---------------------------

- Relaxed Faker package versioning requirement for ``Faker`` (Robin Chow)

2.4.0

---------------------------

- Allowed configuration of the Django settings module to be used via a
commandline argument `286 <https://github.com/PyCQA/pylint-django/issues/286>`_
- If Django settings are not specified via a commandline argument or environment
variable, an error is issued but defaults are loaded from Django, removing the
fatal error behaviour. `277 <https://github.com/PyCQA/pylint-django/issues/277>`_
and `243 <https://github.com/PyCQA/pylint-django/issues/243>`_
- Fixed tests to work with pylint>2.6
- Fixed ``AttributeError: 'Subscript' object has no attribute 'name'`` error.
Closes `284 <https://github.com/PyCQA/pylint-django/issues/284>`_ (uy-rrodriguez)
- Pin Faker version to Prevent Asteroid Crash (James Pulec)
- Remove Python 3.5 Support (EOL since Sept 2020 and Faker requires 3.6 anyway)
(James Pulec)
- Fixed reverse manager ``update_or_create`` calls (James Pulec)

2.3.0

---------------------------

- Improvement in error message for ``missing-backwards-migration-callable``
(Bryan Mutai)
- Start testing with Django 3.1 on Python 3.8
- Better error message when Django is not configured. Closes
`277 <https://github.com/PyCQA/pylint-django/issues/277>`_

2.2.0

---------------------------

- Rely on Django to resolve string references in ForeignKey fields. Refs
`243 <https://github.com/PyCQA/pylint-django/issues/243>`_ (Alejandro Angulo)
- Suppress ``unused-argument`` for functions in migration modules. Fix
`267 <https://github.com/PyCQA/pylint-django/issues/267>`_
- New checker for hard-coded ``auth.User``. Fix
`244 <https://github.com/PyCQA/pylint-django/issues/244>`_
Links

@pyup-bot pyup-bot mentioned this pull request Sep 20, 2024
@pyup-bot
Copy link
Collaborator Author

Closing this in favor of #814

@pyup-bot pyup-bot closed this Sep 24, 2024
@s-m-i-t-a s-m-i-t-a deleted the pyup-update-pylint-2.1.1-to-3.3.0 branch September 24, 2024 12:51
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.

1 participant