MicroPython Forum (Archive)

In device drivers it's common practice to have a substantial number of global constants specifying things like device commands and registers e.g.: Each line causes four bytes of RAM to be used, even if the module is implemented as frozen bytecode. This is because the language requires the variables to be available to other modules even if this is not the designer's requirement. Given the use of MicroPython on resource constrained platforms this seems wasteful.

Would it be feasible to enforce module locality on globals having names starting with an underscore and declared as constant? This would turn a Python naming convention into physical reality, but only when using the const() keyword. This arose from considering a discussion here http://forum.micropython.org/viewtopic. ... nst#p10773

Another alternative would be to not make available names that are not listed in "__all__" for the module -- if it's defined, that is.

Indeed. I have no knowledge of compiler design so I've no idea which would be easier to implement. One arguable advantage to my approach is that, with the change, MicroPython code remains compatible with standard Python by adding