Skip to content

Cleo exceptions don't use pep8 naming conventions (and pep8-naming flake8 plugin doesn't seem to care) #162

Closed

Description

@danieleades

Cleo's exceptions end in the suffix *Exception. PEP8 stipulates that exceptions should end in the suffix *Error. The pep8-naming flake8 extension is installed as a pre-commit hook, but is not triggering (for some reason).

see https://peps.python.org/pep-0008/#exception-names

Activity

  1. Secrus commented on Jul 4, 2022

    @Secrus
    Member

    I investigated this a bit. pep8-naming is adding this error to default ignore of flake8 config here. I think it's to be adjusted in flake8 config.

  2. Secrus commented on Jul 12, 2022

    @Secrus
    Member

    I tried activating the flake8 error, but with no luck. Might be just my lack of experience with configuring flake8. However, I don't think that *Exception is really wrong. I know it's not strictly in line with PEP8, but it's quite common to see it in projects.

  3. added this to the 1.0 milestone on Sep 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions