Pylint regex conflicts with constant naming convention taught in lesson

[3aluw]

In the learning mode "Variables" concept lesson, it is stated that constants should be named in all uppercase with underscores (e.g., NUMBER_OF_BILLS).

However, when following this convention at numbers' concept exercise, Pylint in the provided environment reports the following error:

Variable name "NUMBER_OF_BILLS" doesn't conform to '^[a-z_][a-z0-9_]{1,30}$' pattern

This happens because the Pylint configuration enforces the regex:

variable-rgx=^[a-z_][a-z0-9_]{1,30}$

which only allows lowercase variable names and does not account for uppercase constants.

Expected behavior:
If the course teaches constants should be all uppercase, the Pylint configuration should be updated to allow uppercase names for constants. For example, using something like:

const-rgx=^[A-Z_][A-Z0-9_]{1,30}$

Additional context:
The current mismatch can confuse learners who follow the lesson’s guidance but receive style errors for doing so.

[github-actions]

Hello. Thanks for opening an issue on Exercism 🙂

At Exercism we use our Community Forum, not GitHub issues, as the primary place for discussion. That allows maintainers and contributors from across Exercism's ecosystem to discuss your problems/ideas/suggestions without them having to subscribe to hundreds of repositories.

This issue will be automatically closed. Please use this link to copy your GitHub Issue into a new topic on the forum, where we look forward to chatting with you!

If you're interested in learning more about this auto-responder, please read this blog post.

[IsaacG]

The forum or Discord is the correct place to ask about questions like this :)

NUMBER_OF_BILLS in your code is almost definitely a function variable and not a module constant so the constant naming rules don't apply to it. See PEP-8 for Function and Variable Names and Constants. If you have any further questions, please use the forum or Discord server.

[BethanyG]

Hi @3aluw 👋🏽

Without the full code that triggered the feedback, I have no way of double checking the Analyzer rules. In the future (here or on the forum - the forum MUCH preferred), please provide the code with the feedback so I can troubleshoot. Thanks!

As Isaac has mentioned above, PyLint and our analyzer would likely identify an ALL_CAPS variable that wasn't declared at the module (outside a function or class) level, so it is highly likely that is what it is complaining about (because you should only use the all-caps syntax for constants). But I can't know for sure unless I see the code that triggered it (and create an AST to test the rules).

@IsaacG -- the close message is clear about where to bring up issues for this and the other repos. No need to reply to them (and I'd prefer that you generally don't). 💙 🙂