N816 doesn't flag lower-case variable names

[isaacag]

Context managers are not taken into consideration for variable naming conventions, despite PEP8 not making exceptions for them. The only way to trigger variable rules is to wrap them in other structures like a def.

def example_function():
    Variable = 10 # N806 triggered
    with open('file.txt') as file:
        Variable = file.read() # N806 triggered

with open('file.txt') as file:
    Variable = file.read() # No rule triggered

[MichaReiser]

The current behavior makes sense to me, considering that the rule is about variable names in functions and doesn't enforce lower case variable names in general.

Checks for the use of non-lowercase variable names in functions.

And Variable in the second example is a variable in the module scope.

[isaacag]

If possible I think it would be nice to have an additional rule covering those cases, even if is another scope.

[MichaReiser]

If possible I think it would be nice to have an additional rule covering those cases, even if is another scope.

There's https://docs.astral.sh/ruff/rules/mixed-case-variable-in-global-scope/ but it doesn't forbid using variable names that start with an uppercase character. I'm not sure why is but the rule matches the behavior of the upstream rule PyCQA/pep8-naming#69

[isaacag]

That is odd, docs leave the impression that any non snake case variables will trigger the rule.

[MichaReiser]

I merge this with #15069 that lists a few reasons