Justin-Fisher

Okay, I think there is one fairly small sort of backwards-incompatibility that I may want to insist upon. Traditionally, `controller.py` stored a bunch of NodeType constants (like `WB_NODE_ACCELEROMETER`) as simple...

I think that since it crashes, that means it's actually broken. It may be that the decision will be that one shouldn't be able to fetch values from such fields,...

If we can't figure out a way to (1) make swig automatically generate appropriate python type hints (and my sense from reading threads like the one @omichel linked is that...

My current way of using supervisor controllers in Python works much like you suggest with getters and setters to let me use simple `.attribute` notation to get/set the fields of...

Making controller.py be manually maintained would indeed open the door to a number of useful things, including (1) type-hinting for python linters, (2) adding helpful python doc-strings, and (3) providing...

I think there is a swig option to have it generate auto-documentation, which is often flawed (e.g., using C++ names for types rather than their Python names) but still could...

Ironically enough, last year I pointed out that specific flavors of `getDevice` functions like `getMotor` weren't really needed, when there was already a one-size-fits-all `getDevice` function that yielded exactly the...

Another thing I've been thinking about folding into a new-and-improved controller.py is to include a Vector class that I created to use as the default format for various Webots functions...

(Incidentally, I implement Vectors as a subclass of Python Lists, so changing any part of the API that previously returned Lists to instead return Vectors should be fully backwards-compatible, since...

Before embarking on this, I should probably try to get clear on something else you said above, suggesting that we might want to use the C API instead of the...