Consistent naming of Micro Python

[Damien]

Before it's too late, we should decide on a consistent naming style for the phrase "Micro Python". I've been using "Micro Python" with a space whenever I write it, but I realise that a lot of others are writing it as "MicroPython" (no space). Also I see "Micropython" and "microPython" sometimes. And there's "uPy", but that's a short-hand name and is being used quite consistently already.

I personally prefer "Micro Python".

[pfalcon]

I prefer "MicroPython". That's more search-friendly, and potentially, there're less "trademark" confusion, after all, "MicroPython" is a different word than "Python". And MicroPython and Python are different languages, so PSF may ask to use different name.

[dhylands]

I agree - especially on differentiating for search.

[mad474]

Also prefer "MicroPython" because of aforementioned and beyond
- its in use in my docs
- its a bit more micro than "Micro Python" (or say a few bits ...)
- CamelCase is somehow associated with programming
but I'm neither defined nor is my opinion significant

[Damien]

Thanks for quick feedback. I agree one word "MicroPython" really glues the Micro to the Python and defines it as its own entity/language. Let's go with no space then.

[cloudformdesign]

To be in line with CPython, I would just call it uPython. Simple, concise and recognizable. You could also call it Uython to be in line with Jython and Cython, but that is unpronounceable, so I would advise against it

[cloudformdesign]

Just to be sure, the final name is MicroPython, with CAPS and everything. I've been doing a massive overhaul of the wiki and I want to make sure this is right.

I personally like keeping the names of things that are "micro" smaller, such as upy or upython -- but that's just me. It's your project!