Justin-Fisher

The main reason I see is inertia: we already have a working `controller.py` using the C++ API, and it would take effort to change which API it uses. That effort...

Another relevant question is what version(s) of Python we'll be aiming to support? There's a fairly deep division in the Python community between people who use a quite new version...

The code I'm aiming to integrate does currently use some features from 3.8+, but it should be fairly straightforward to rewrite it to work with 3.7 or even 3.6. The...

In case it got lost in the ensuing discussion of python versions, I'll repeat a couple of my questions from earlier: > On the bright side, I think the tasks...

Sorry if I'm being slow/dense on this. Are you talking about libController.a? Do you know how to import that in Python? And how to access the relevant functions in Python?...

My windows installation has `libController.a` and `controller.dll`, but not `libController.dll` (at least not in the controller folder). For now I think I'll stick with the swig/C++ API, though I've been...

I don't suppose you know already what type the "WbDeviceTag" returned by `wb_robot_get_device` will have when it gets passed from the C API to python? Just an integer?

The old `controller.py` includes some functions that return device tags, e.g. `Brake.getMotorTag`, but these generally don't seem to be documented in Webots docs for the Python API. Is it fine...

Here's a partial workaround (written as an overwritten method in a subclass of `Robot` as that was easiest for me to test). This is unfortunate in that (a) it duplicates...