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

Open

opened

on Apr 17, 2019

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

to join this conversation on GitHub. Already have an account? Sign in to comment

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