Kilon has https://github.com/kilon/Atlas. It would be good to explain the difference/tradeoff/motivation/etc to create another bridge.
There is this from Pharo Users:
I know a little Kilon’s bridge as I used it as backend for Python3Generator [1] in the beginning.
To my understanding , the difference is that Atlas is lower-level than PythonBridge.
Basically, Atlas allows one to send python string and get back the returned value if it is a primitive type (int, float, str, etc).
PythonBridge uses Python3Generator as DSL to build valid Python code. Atlas expects regular Pharo’s string.
PythonBridge provides debugging facilities, Atlas does not to my knowledge.
PythonBridge provides facilities to map Pharo classes to Python classes, Atlas does not.
...
Links:
[1]: https://github.com/juliendelplanque/Python3Generator
Julien Delplanque
After reading that I wonder if there could be any benefit to using Atlas underneath instead of maintaining two low level supports
Kilon has https://github.com/kilon/Atlas. It would be good to explain the difference/tradeoff/motivation/etc to create another bridge.
There is this from Pharo Users:
After reading that I wonder if there could be any benefit to using Atlas underneath instead of maintaining two low level supports