Conventions for python names

By default, we should strive to follow PEP8 :

• Class names should normally use the CapWords convention
• Function and method names should be lowercase, with words separated by underscores
• Variable names follow the same convention as function names

The above conventions do not apply to functions and classes that interface with ASP:

• functions that are called from asp
• • start with python
• • use mixed case
• • are located in a #script (python) section of some .lp file
• asp predicates or function symbol of arity zero
• • are typically member of an enumeration class
• • are uncapitalized
• • use the same name as the corresponding asp name
• • use that name for the enumeration member whenever possible
• classes that correspond to asp predicates or function symbol of non-zero arity
• • typically derive from NamedTuple
• • start with an uppercase letter
• • using the same name as the corresponding asp name (the capitalization of the first letter notwithstanding)

Examples:

• evaluate_expr is function that is not interfacing with asp
• pythonEvalExpr is an interface function
• the python class Set_value derives from NamedTuple and has 3 attributes. It corresponds to the asp set_value/3 predicate;
• the enumeration member SetOperator.fold corresponds to the asp fold predcate. Its name is "fold"

No files, tests, or entry points are named. First inspect the repository's Python sources and determine whether the conventions are intended to be documented or applied across existing code. The issue does not define a verifiable done state.