Forbid types in variable name

Rule request

Thesis

Forbid using built-in type name in the variable name, either as prefix or suffix. It applies to all variable definitions: function arguments, assignments, with.

# bad
username_str = 'root'
username_str = current_user()
USERNAME_STR = 'root'
str_username = 'root'

# good
username = current_user()
username: str = current_user()
stranger = 'root'
default_user = User()

The rule should be applied to built-in types only: str, int, float, set, dict, and so on. Having context = Context() is fine.

Reasoning

Type annotations are better, they can be statically checked. Names can get outdated.

[orsinium]

Good point. Let’s try to classify then

• Abbreviated, can be safely banned: int (integer), bool (boolean), dict (dictionary).
• Joined words, can be banned: frozenset (frozen set), bytearray (byte array).
• Real words but rarely used, consider banning: float (hard to imagine context where it means something except floating point number), tuple (I know it is used for database entities but word “record” is a better synonym), bytes (can be something like “bytes_count”, probably), complex (same as float, what else can be complex if not numbers).
• Real words, proceed carefully: set, list, slice, type, range.

[sobolevn]

It can have other types as well, for example: module_list = ModuleList()