Codecov Report

Merging #8905 (03329f1) into main (6dac300) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main    #8905    /-   ##
=======================================
  Coverage   95.75%   95.75%           
=======================================
  Files         173      173           
  Lines       18652    18655     3     
=======================================
  Hits        17860    17863     3     
  Misses        792      792           

There’s 2 warnings in the readthedocs output that are failing the ci but unsure which file it’s coming from exactly. Seems to be 3.0/index

I'm going to try to fix the readthedoc pipeline on main.

Well it was due to,

/home/docs/checkouts/readthedocs.org/user_builds/pylint/checkouts/8905/doc/whatsnew/3/3.0/index.rst:107: WARNING: Bullet list ends without a blank line; unexpected unindent.

/home/docs/checkouts/readthedocs.org/user_builds/pylint/checkouts/8905/doc/whatsnew/3/3.0/index.rst:112: WARNING: Bullet list ends without a blank line; unexpected unindent.

It was fixed by @jacobtylerwalls in #8921, so rebasing should work, thank you Jacob :)

🤖 Effect of this PR on checked open source code: 🤖

Effect on music21: The following messages are now emitted:

1. invalid-name:
   Class attribute name "registerOutputSubformatExtensions" doesn't conform to '([A-Za-z][A-Za-z0-9_]{2,30}|(._))$' pattern*
   https://github.com/cuthbertLab/music21/blob/8baa27339109895cc4c55dd99cb0290e111fb02a/music21/converter/subConverters.py#L355
2. invalid-name:
   Class attribute name "registerOutputSubformatExtensions" doesn't conform to '([A-Za-z][A-Za-z0-9_]{2,30}|(._))$' pattern*
   https://github.com/cuthbertLab/music21/blob/8baa27339109895cc4c55dd99cb0290e111fb02a/music21/converter/subConverters.py#L411
3. invalid-name:
   Class attribute name "registerOutputSubformatExtensions" doesn't conform to '([A-Za-z][A-Za-z0-9_]{2,30}|(._))$' pattern*
   https://github.com/cuthbertLab/music21/blob/8baa27339109895cc4c55dd99cb0290e111fb02a/music21/converter/subConverters.py#L834

This comment was generated for commit 83a3503

These seem valid because the names are too long for the regex defined in that project's pylintrc:

import re
>>> re.match("([A-Za-z_][A-Za-z0-9_]{2,30}|(__.__))$", "registerOutputSubformatExtensions")
>>> 
>>> re.match("([A-Za-z_][A-Za-z0-9_]{2,30}|(__.__))$", "registerOutputSubformatExtensio")
<re.Match object; span=(0, 31), match='registerOutputSubformatExtensio'>
>>> 

@Pierre-Sassoulas in the context of the example you refer to, the message doesn't raise and that is the expected outcome since the members satisfy the checker and the attributes are not assigned values (hence they don't appear in the __members__ container). However, you need to also checkout the astroid branch pylint-dev/astroid#2263 to see it working correctly.

from enum import Enum

class AnEnum(Enum):
    apple: int
    PEAR: int = 42


print(AnEnum.__members__)
{'PEAR': <AnEnum.PEAR: 42>}

Let's add a lower-cased purple member to the example:

from enum import Enum

class Color(Enum):
    """Represents colors as (red, green, blue) tuples."""

    YELLOW      = 250, 250,   0
    KHAKI       = 250, 250, 125
    MAGENTA     = 250,   0, 250
    VIOLET      = 250, 125, 250
    CYAN        =   0, 250, 250
    AQUAMARINE  = 125, 250, 250
    purple      = 1, 2, 3

    # Class constant name "red" doesn't conform to UPPER_CASE naming style (invalid-name)
    # Class constant name "green" doesn't conform to UPPER_CASE naming style (invalid-name)
    # Class constant name "blue" doesn't conform to UPPER_CASE naming style (invalid-name)
    red: int
    green: int
    blue: int

    def __init__(self, red: int, green: int, blue: int) -> None:
        self.red   = red
        self.green = green
        self.blue  = blue

    @property
    def as_hex(self) -> str:
        """Get hex 'abcdef' representation for a color."""
        return f'{self.red:0{2}x}{self.green:0{2}x}{self.blue:0{2}x}'

example.py: 12:4: C0103: Class constant name "purple" doesn't conform to UPPER_CASE naming style (invalid-name)

Unittests will fail now until pylint-dev/astroid#2263 is released.
About that - I currently have the astroid change set for 3.0 release but would you prefer that to be changed to 2.15.7 instead?

Is it a bug fix il astroid ? If so we can backport it. If not let's release this in 3.0

Is it a bug fix il astroid ? If so we can backport it. If not let's release this in 3.0

It's a bug-fix in both astroid and Pylint (if I've understood you correctly :))
astroid fix: exclude non-members from __members__ (i.e: tomato: int)
pylint fix: check that the AssignName belongs to the __members__ of it's class (and not only check that the class is a subtype of enum.Enum.)

I liked your own functional test too, we can have both :) otherwise LGTM

No worries - less is more :)

Blocked by the releease of astroid 2.15.7 then ?

It's also blocked by #8897 since the code in that example when run with the Pylint code of the current MR crashes 😢

It's also blocked by #8897 since the code in that example when run with the Pylint code of the current MR crashes 😢

But I may have a fix for that shortly :)

🤖 Effect of this PR on checked open source code: 🤖

Effect on home-assistant:
The following messages are no longer emitted:

Effect on music21:
The following messages are now emitted:

Effect on django:
The following messages are no longer emitted:

This comment was generated for commit 03329f1

@mbyrnepr2 do you know why tests are passing without your astroid changes here? 🙏

I think the changes from astroid were pulled in from latest push? 2.15.7 astroid went out last month I think. There’s been a couple of different enum changes.

2.15.7 went out yesterday, and we haven't updated pylint to that or created a new astroid pre-release (but hoping to do so soon)

Ooh, Pierre is doing the pre-release right now!

We have both 2.15.7 and 3.0.0b0 released now, so it should be possible to merge on main then backport.