reportPrivateUsage
behaves differently when a global variable is modified inside a method on a class
#679
Labels
type checking / linting
issues relating to existing diagnostic rules or proposals for new diagnostic rules
upstream bug
a bug that also exists in pyright but has not been raised upstream
i think ideally it should only complain on the import. suppressing the error there should be enough to tell the type checker that you're using a private variable intentionally
The text was updated successfully, but these errors were encountered: