On Wednesday, November 2, 2016 at 11:35:20 AM UTC-4, Daniel Carrera wrote: > > Here is an idea for the future: Is it possible to get PyCall to print the > rest of Python's error message so that dummies like me aren't led astray... > It's weird that most of the error was printed but the path to the file was > not. >
Could you file an issue, maybe with test code via pyeval or something, that illustrates the problem? Maybe there is a separate Python API function that I should be using to display exception output.
