Skip to content

move PythonEval::build_python_error_message to separate header for reuse #93

@noskill

Description

@noskill

build_python_error_message and throw_on_error from PythonEval.cc looks quite useful for all code working with python c-api. Not sure if it should be moved to coguitls or just separate header in atomspace

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions