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

[Backport maintenance/2.17.x] Fix incorrect preferred-modules matches #8481

Merged

Conversation

github-actions[bot]
Copy link
Contributor

Backport d64c0cc from #8454.

Co-authored-by: d33bs <[email protected]>
(cherry picked from commit d64c0cc)
@DanielNoord DanielNoord reopened this Mar 21, 2023
@DanielNoord
Copy link
Collaborator

@Pierre-Sassoulas Do we even merge this now that we have cut off 3.x?

@codecov
Copy link

codecov bot commented Mar 21, 2023

Codecov Report

Merging #8481 (1744f99) into maintenance/2.17.x (d6f3ae8) will not change coverage.
The diff coverage is 100.00%.

Additional details and impacted files

Impacted file tree graph

@@                 Coverage Diff                 @@
##           maintenance/2.17.x    #8481   +/-   ##
===================================================
  Coverage               95.56%   95.56%           
===================================================
  Files                     178      178           
  Lines                   18779    18779           
===================================================
  Hits                    17947    17947           
  Misses                    832      832           
Impacted Files Coverage Δ
pylint/checkers/imports.py 94.34% <100.00%> (ø)

@Pierre-Sassoulas
Copy link
Member

Yes 2.17 is the last minor. The question is more 'should we keep two minors maintenance branch once 3.0.0 is out ?'. I think we should keep the possibility but I don't think it's that valuable for users frankly.

@Pierre-Sassoulas Pierre-Sassoulas merged commit 7d26dcf into maintenance/2.17.x Mar 22, 2023
@Pierre-Sassoulas Pierre-Sassoulas deleted the backport-8454-to-maintenance/2.17.x branch March 22, 2023 07:32
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.

2 participants