In the grounding, rules are created stating:
_execution_exec("c0"),error(statement(pythonError),"(Statement(symbol=<StatementWarning.pythonError: 'pythonError'>), NameError(\"name 'x' is not defined\"))")):-_execution_mapped("c0"),()).
when using a statement_python and the variable is clearly declared as input for the execution_declare.
A similar error is:
TypeError(\"'>=' not supported between instances of 'NoneType' and 'int'\"))")
As apparently None is some kind of default.
This is technically not wrong but could probably be improved.
In the grounding, rules are created stating:
_execution_exec("c0"),error(statement(pythonError),"(Statement(symbol=<StatementWarning.pythonError: 'pythonError'>), NameError(\"name 'x' is not defined\"))")):-_execution_mapped("c0"),()).when using a statement_python and the variable is clearly declared as input for the execution_declare.
A similar error is:
TypeError(\"'>=' not supported between instances of 'NoneType' and 'int'\"))")As apparently None is some kind of default.
This is technically not wrong but could probably be improved.