error returns stacktrace string instead of traceback object #57
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What used to be:
Upon Python errors Erlang receives an opaque traceback object as binary data. It can be decoded to ASCII as readable text, but it has to be done manually and the non-text bytes obstruct readability.
With this modification:
Erlang now receives the text representation of the traceback as readable binary string.
Better for debugging python processes, better for displaying meaningful error messages to users.