Replacing do_project_a and do_project_b with Custom Snake Case Code Works

As title. When I started to learn Python, I preferred to use snake case for vars and lower camel case for functions, to better distinguish them. Why in PEP 8 it was preferred to use an unique style for vars and funcs?

It is a commonly used naming convention in computing, for example for variable and subroutine names, and for filenames. One study has found that readers can recognize snake case values more quickly than camel case. However, "subjects were trained mainly in the underscore style", so the possibility of bias cannot be eliminated. A variation is screaming snake case, where words are written in all caps (stylized as SCREAMING_SNAKE_CASE). This convention is used for constants in programming languages like C/C++, Python, Java, PHP, as well as for environment variables.

In Python, this style is generally deemed unnecessary because attribute and method names are prefixed with an object, and function names are prefixed with a module name. In addition, the following special forms using leading or trailing underscores ...

def valid_snake_case(arg): ... def InvalidCamelCase(arg): ... def more_valid_snake_case(arg): ... Because of this, the name on line 4 will trigger an invalid-name warning, even though the name matches the given regex. Matches named exempt or ignore can be used for non-tainting names, to prevent built-in or interface-dictated names to trigger certain naming styles. ... Format: comma-separated groups of colon-separated names. This option can be used to combine name styles. For example, function:method enforces that functions and methods use the same style, and a style triggered by either name type carries over to the other.

The main purpose of snake case is to improve code readability. By separating words with underscores, it becomes easier to distinguish between different parts of a name, especially when the name is long. This convention is used for naming variables, functions, and non-public class attributes ...

Now, based on the language you're working on and what you're naming, the preferred case type can change. For example, according to the PEP 8 – Style Guide for Python Code, variable and function names should use snake case:

In programming, snake case is a naming convention where you write compound names by joining words with underscores (_) and using only lowercase letters. Using underscores to separate words in an identifier improves readability.

Which is absolutely contradictory with the fact that a camel cased group of words form an unambiguous solid symbol that looks like a single object matching the idea that a method name is one thing (as opposed to several objects, words, that have to be read and later interpreted as one single group of several things). That's even worst for _ if the method name contains a reserved word in it. 2015-03-19T02:15:10.25Z+00:00 ... Of course, Python uses snake_case.

Variable, method, and function names should always be snake_case (wonder where it got that name?). You'll see camelCase in some really old Python code but it's not the modern convention at all.