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.

Cheers,

Julien

Links:
[1]: https://github.com/juliendelplanque/Python3Generator


---
Julien Delplanque
Doctorant �� l���Universit�� de Lille
B��timent B 40, Avenue Halley 59650 Villeneuve d'Ascq
Num��ro de t��l��phone: +333 59 35 86 40

Le 28 juin 2019 �� 03:49, Alexandre Bergel via Pharo-users <pharo-users@lists.pharo.org> a ��crit :


De: Alexandre Bergel <alexandre.bergel@me.com>
Objet: R��p : Python bridges
Date: 28 juin 2019 �� 03:49:20 UTC+2
��: Ben Coman <btc@openinworld.com>
Cc: Any question about pharo is welcome <pharo-users@lists.pharo.org>



How does usage of your Python bridge compare to Kilon's... ?

No idea. But our bridge adequately manages errors crossing language boundaries and employ a set of command to enable promises. I am not sure sure whether Atlas was designed to do so.

Alexandre