This is a ticket to collect ideas about, and prepare for, v2.0 of MicroPython. It won't be at least until Jan 2017 that this version will be released.

Changing a major version means that we are allowed to "break" compatibility. Although this is not something to aim for it would be a good chance to resolve the following issues (one way or another):

• RFC: Cleaning up macro naming, possibly switch to inline functions #293 clean up macro names - now done
• mp_ prefix collision #704 change mp_ prefix
• Move ports to subdirectory #2401 move all ports to a subdirectory - now done

It would also be nice to have Python 3.5 "compatibility" (see #1329) by v2.0.