Grumpy's runtime library implements a Python call stack, complete with exceptions. It would probably require a lot of abuse (if it's even possible) to support Python's exception/traceback APIs using Go's native call stack (I.e., not building a call stack atop Go's).
I see. That will probably add a huge performance hit (compared to actually calling native code functions) but oh well. Not that different from what CPython is already doing.
Think of it like TypeScript->ES6 transpilation -- you don't have to use Go to write Go apps, but instead Go-based Python.
Error handling will have to be Go-like though, so handling return values instead of raised exceptions.
[deleted] 1 points · Jan 2017
Not sure how it actually works, but maybe exceptions can be faked on Go with Panic()/Recover()
weberc2 1 points · Jan 2017
Grumpy's runtime library implements a Python call stack, complete with exceptions. It would probably require a lot of abuse (if it's even possible) to support Python's exception/traceback APIs using Go's native call stack (I.e., not building a call stack atop Go's).
[deleted] 1 points · Jan 2017
I see. That will probably add a huge performance hit (compared to actually calling native code functions) but oh well. Not that different from what CPython is already doing.