Suggestion conflicting with black 2024 style for inlined semantic / empty classes

[Pierre-Sassoulas]

Bug description

class DebugTrueDetected(Exception): ...

Command used

pylint a.py

Pylint output

C0321: More than one statement on a single line (multiple-statements)

Expected behavior

No conflict with black I guess ?

Pylint version

pylint 3.0.3

[jacobtylerwalls]

Figure we should exempt Ellipsis and Pass from the calculation.

[mbyrnepr2]

black moves pass to the next line in this example, so might want to focus on ... only?

class Apple: pass

[jacobtylerwalls]

Either way, but I don't think it hurts to exempt pass from the pylint check. I'm surprised black treats them differently.

[Pierre-Sassoulas]

Agree with @jacobtylerwalls, let's make pylint consistent for those not using black.

[Pierre-Sassoulas]

After looking into it, a good half of our examples and functional tests are just something with pass at the end. We might want to add an option to permit to still raise for pass or ... ?

[jacobtylerwalls]

Are we sure that's not just a shortcut taken by test authors? Is there any original discussion about the check?

[Pierre-Sassoulas]

So it seems it's a decision that was done a long time ago but not in Logilab so we have a little context, I've done a little lot of digging and the functional test come from 0781e73 and the original file was renamed here ee2571c, then #3224 happened, and was moved previously here 33b8185, #2236 happened, moved in 26eb7f9 and in 170b305 . Then the history of the antique test/test_format.py point to f1209f5. Maybe there's more info on bitbucket (can't find the repo though) but it seems Jacob's hypothesis is likely.