Re:Micro Python – a lean and efficient implementation of Pyt...
by AceJohnny2 on Tuesday June 03, 2014 @02:01PM
(#7841762)
> The biggest difference listed is probably no Unicode.
Funny, considering that was the core reason for Python3 in the first place (though I can't immediately come up with a reference).
Re:Micro Python – a lean and efficient implementation of Pyt...
by maxerickson on Tuesday June 03, 2014 @02:05PM
(#7841789)
This is sort of the design document for Python 3:
http://legacy.python.org/dev/peps/pep-3100/
Along with this one:
http://legacy.python.org/dev/peps/pep-3000/
(Of course there was lots and lots of thought and discussion that is not reflected in those documents)
I would characterize the Unicode/bytes change to simply be the most visible and disruptive change, it didn't really stand apart as far as being a reason, it was one of many.
Re:Micro Python – a lean and efficient implementation of Pyt...
by AceJohnny2 on Tuesday June 03, 2014 @02:34PM
(#7841970)
From what I remember from various posts, most other changes could be done gradually on the 2.x branch. Unicode couldn't.
I may be mischaracterising it :)
That said, I suppose it's wise to base MicroPython on the "live" branch of Python (3.x), not the legacy one (2.x), even if Unicode support is too costly for them.
https://github.com/micropython/micropython/wiki/Differences
But I guess they are still in the process of writing that/filling it out.
The biggest difference listed is probably no Unicode. Another significant point is that lots of library functions are only partially implemented.