# Variable naming
- Must
- start with `_ a-z A-Z`
- followed can use `_ 0-9 a-z A-Z`
- cannot be reserved words
- Convertions
- `_my_var` : This is a convention to indicate orvgte objects Objects named this way will not get imported by a statement such as: `from module tmport`
- `__my_var` : Used to 'mangle" class attributes useful in inheritance chains
- `__my_var__` : Used for system-defined names that have a special meaning to the interpreter.
- Packages : short, all-Howercase names. Preferably no underscores. e.g. `utilities`
- Modules : short, allHowercase names. Can have underscores. e.g. `db_var`
- Classes : CapWords (upper camel case) convention, e.g. `MyClass`
- Functions lowercase, words separated by underscores (snake_case) e.g. `my_func`
- Variables lowercase, words separated by underscores (snake case) e.g. `my_var`
- Constants all-uppercase, words separated by underscores. e.g. `CONT_A`