Skip to content

Conversation

@mbyrnepr2
Copy link
Member

@mbyrnepr2 mbyrnepr2 commented Jan 14, 2023

Type of Changes

Type
🐛 Bug fix
✨ New feature
🔨 Refactoring
📜 Docs

Description

Closes pylint-dev/pylint#5719

@Pierre-Sassoulas Pierre-Sassoulas added this to the 2.13.3 milestone Jan 14, 2023
Copy link
Collaborator

@DanielNoord DanielNoord left a comment

Choose a reason for hiding this comment

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

I like the test, very elegant!

Couple of nits, rest LGTM!

@mbyrnepr2
Copy link
Member Author

Thanks for those suggestions @DanielNoord; nothing I can disagree with there!

Copy link
Collaborator

@DanielNoord DanielNoord left a comment

Choose a reason for hiding this comment

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

I'd like to see coverage, but other than that this LGTM!

@codecov
Copy link

codecov bot commented Jan 15, 2023

Codecov Report

Merging #1967 (a48aa4d) into main (49691cc) will decrease coverage by 0.00%.
The diff coverage is 88.88%.

❗ Current head a48aa4d differs from pull request most recent head bc82724. Consider uploading reports for the commit bc82724 to get more accurate results

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main    #1967      +/-   ##
==========================================
- Coverage   92.63%   92.63%   -0.01%     
==========================================
  Files          94       94              
  Lines       10869    10885      +16     
==========================================
+ Hits        10069    10083      +14     
- Misses        800      802       +2     
Flag Coverage Δ
linux 92.39% <88.88%> (-0.01%) ⬇️
pypy 88.54% <88.88%> (-0.01%) ⬇️
windows 92.31% <88.88%> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
astroid/brain/brain_namedtuple_enum.py 92.95% <83.33%> (-0.45%) ⬇️
astroid/raw_building.py 92.30% <100.00%> (+0.13%) ⬆️

@DanielNoord
Copy link
Collaborator

@mbyrnepr2 Do you think you can get the diff coverage to 100% here?

Copy link
Collaborator

@DanielNoord DanielNoord left a comment

Choose a reason for hiding this comment

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

Thanks for the additional test!

@DanielNoord DanielNoord enabled auto-merge (squash) January 15, 2023 17:19
@DanielNoord DanielNoord disabled auto-merge January 15, 2023 17:26
@DanielNoord DanielNoord merged commit c267397 into pylint-dev:main Jan 15, 2023
@github-actions
Copy link
Contributor

The backport to maintenance/2.13.x failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-maintenance/2.13.x maintenance/2.13.x
# Navigate to the new working tree
cd .worktrees/backport-maintenance/2.13.x
# Create a new branch
git switch --create backport-1967-to-maintenance/2.13.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 c267397eda848544bcbea04e889815ac4faa6ba8
# Push it to GitHub
git push --set-upstream origin backport-1967-to-maintenance/2.13.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-maintenance/2.13.x

Then, create a pull request where the base branch is maintenance/2.13.x and the compare/head branch is backport-1967-to-maintenance/2.13.x.

@mbyrnepr2 mbyrnepr2 deleted the pylint_issue_5719 branch January 15, 2023 17:32
@DanielNoord
Copy link
Collaborator

@mbyrnepr2 Could you try and backport this? For some reason git doesn't recognize the maintenance branch for me locally.

@Pierre-Sassoulas Pierre-Sassoulas added the Needs backport Needs to be cherry-picked on the current patch version by an astroid's maintainer label Jan 17, 2023
mbyrnepr2 added a commit that referenced this pull request Jan 18, 2023
Co-authored-by: Daniël van Noord <[email protected]>
(cherry picked from commit c267397)
@mbyrnepr2
Copy link
Member Author

Done @DanielNoord: #1971. Let me know if any issues.

@DanielNoord
Copy link
Collaborator

Thanks! I feel bad for asking, but could you do #1970 as well? 😄

It's my own PR but I haven't been able to fix the broken git remote issue on my local machine.. 😅

DanielNoord added a commit that referenced this pull request Jan 18, 2023
Co-authored-by: Daniël van Noord <[email protected]>
(cherry picked from commit c267397)
@Pierre-Sassoulas Pierre-Sassoulas removed the Needs backport Needs to be cherry-picked on the current patch version by an astroid's maintainer label Jan 18, 2023
@cdce8p cdce8p added the backported Assigned once the backport is done label Jan 31, 2023
@cdce8p cdce8p modified the milestone: 2.13.3 Jan 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backported Assigned once the backport is done Bug 🪳

Projects

None yet

Development

Successfully merging this pull request may close these issues.

enum.Enum type is blindly assigned to "Enum" of other modules

4 participants