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.

Sign up for GitHub

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

Jump to bottom

Support for django 5.1, use pylint 3.0+, drop python 3.8 following EOL 2024-10-07 #437

Merged
merged 2 commits into from
Oct 9, 2024
Merged

Support for django 5.1, use pylint 3.0+, drop python 3.8 following EOL 2024-10-07 #437

merged 2 commits into from
Oct 9, 2024

Conversation

Pierre-Sassoulas
Copy link
Member

@Pierre-Sassoulas Pierre-Sassoulas commented Oct 8, 2024 •
edited
Loading

Refs #432 (3.13 will be dealt with later on in #440).

@coveralls
Copy link

coveralls commented Oct 8, 2024 •
edited
Loading

Pull Request Test Coverage Report for Build 11261269987

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 85.27%
Totals Coverage Status
Change from base Build 11260997911: 0.0%
Covered Lines: 741
Relevant Lines: 869
💛 - Coveralls

@Pierre-Sassoulas Pierre-Sassoulas changed the title Support for python 3.12, 3.13, django 5.1, pylint 3.0+, remove python 3.7, and 3.8 Support for python 3.13, django 5.1, pylint 3.0+, remove python 3.7, and 3.8 Oct 8, 2024
Pierre-Sassoulas
Pierre-Sassoulas commented Oct 8, 2024
View reviewed changes
Copy link
Member Author

@Pierre-Sassoulas Pierre-Sassoulas left a comment •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't have to drop python 3.8 yet, it's been EOL for 1 day and we didn't release for a long time. tests don't work, dropped.

tox.ini Show resolved Hide resolved
tox.ini Outdated Show resolved Hide resolved
@Pierre-Sassoulas Pierre-Sassoulas changed the title Support for python 3.13, django 5.1, pylint 3.0+, remove python 3.7, and 3.8 Support for python 3.13, django 5.1, pylint 3.0+ Oct 8, 2024
@Pierre-Sassoulas Pierre-Sassoulas added this to the 2.6.0 milestone Oct 9, 2024
@Pierre-Sassoulas Pierre-Sassoulas changed the title Support for python 3.13, django 5.1, pylint 3.0+ Support for django 5.1, pylint 3.0+, drop support for python 3.8 following EOL 2024-10-07 Oct 9, 2024
@Pierre-Sassoulas Pierre-Sassoulas changed the title Support for django 5.1, pylint 3.0+, drop support for python 3.8 following EOL 2024-10-07 Support for django 5.1, use pylint 3.0+, drop support for python 3.8 following EOL 2024-10-07 Oct 9, 2024
@Pierre-Sassoulas Pierre-Sassoulas changed the title Support for django 5.1, use pylint 3.0+, drop support for python 3.8 following EOL 2024-10-07 Support for django 5.1, use pylint 3.0+, drop python 3.8 following EOL 2024-10-07 Oct 9, 2024
@Pierre-Sassoulas Pierre-Sassoulas merged commit 745f803 into pylint-dev:master Oct 9, 2024
31 checks passed
@Pierre-Sassoulas Pierre-Sassoulas deleted the drop-3.7-add-3.12-3.13 branch October 9, 2024 19:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
2.6.0
Development

Successfully merging this pull request may close these issues.
2 participants
@Pierre-Sassoulas @coveralls