Consistent naming of Micro Python

C programming, build, interpreter/VM.
Target audience: MicroPython Developers.
Post Reply
Damien
Site Admin
Posts: 619
Joined: Mon Dec 09, 2013 5:02 pm

Consistent naming of Micro Python

Post by Damien » Sun Feb 01, 2015 1:45 pm

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
Posts: 1155
Joined: Fri Feb 28, 2014 2:05 pm

Re: Consistent naming of Micro Python

Post by pfalcon » Sun Feb 01, 2015 5:18 pm

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.
Awesome MicroPython list
Pycopy - A better MicroPython https://github.com/pfalcon/micropython
MicroPython standard library for all ports and forks - https://github.com/pfalcon/micropython-lib
More up to date docs - http://pycopy.readthedocs.io/

User avatar
dhylands
Posts: 3227
Joined: Mon Jan 06, 2014 6:08 pm
Location: Peachland, BC, Canada
Contact:

Re: Consistent naming of Micro Python

Post by dhylands » Sun Feb 01, 2015 6:32 pm

I agree - especially on differentiating for search.

mad474
Posts: 60
Joined: Sun Dec 29, 2013 7:48 pm

Re: Consistent naming of Micro Python

Post by mad474 » Sun Feb 01, 2015 6:45 pm

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
Site Admin
Posts: 619
Joined: Mon Dec 09, 2013 5:02 pm

Re: Consistent naming of MicroPython

Post by Damien » Sun Feb 01, 2015 10:22 pm

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
Posts: 35
Joined: Wed Mar 11, 2015 7:48 pm

Re: Consistent naming of Micro Python

Post by cloudformdesign » Wed Mar 11, 2015 7:49 pm

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 :D

cloudformdesign
Posts: 35
Joined: Wed Mar 11, 2015 7:48 pm

Re: Consistent naming of Micro Python

Post by cloudformdesign » Thu May 07, 2015 7:59 pm

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!

Post Reply