Olivier Michel

I believe the problems come from the scoping of these constants. In C and Matlab, no scoping is possible hence all the constants are defined at a global scope. In...

Regarding constants, I don't see the point of having this `WB_CONSTANTS.py` file where we need to manually (or via a python script) maintain values that are redundant with the ones...

> So, that's how I'm tentatively planning to proceed, unless I hear objections? About explicit imports, can't we consider that: ```python from webots import * ``` should be used by...

There are not too many constants to export from C and I am happy to do this, so you can consider this will be done early next week.

Many questions... First of all, I believe we should simply forget about backwards compatibility. I am sure we are going to break it anyhow, so let's break it one for...

We use swig to generate the Python API from the C++ API and there is no easy way to introduce type annotations there, see https://github.com/swig/swig/issues/735 for a discussion on this...

All what you propose should be easy to implement if we totally get rid of swig for generating the Python API. I believe more and more that a totally new...

That's a very nice contribution, but it looks like a helper for the supervisor API, not a replacement of the python controller library. My idea was to replace the swig-generated...

I believe the maintenance overhead for a new python library without swig (let's call it native) is very small. We do not add API functions everyday and whenever we add...

Your type hinting suggestion sounds very good to me. About adding the `interval` optional argument, this is also a very good idea. However, it may be a problem with some...