On Wed, Jun 4, 2014 at 9:12 PM, Paul Sokolovsky email@example.com wrote:
An alternative view is that the discussion on the tracker showed Python developers' mind-fixation on implementing something the way CPython does it. And I didn't yet go to that argument, but in the end, MicroPython does not try to rewrite CPython or compete with it. So, having few choices with pros and cons leading approximately to the tie among them, it's the least productive to make the same choice as CPython did.
I'm not a CPython dev, nor a Python dev, and I don't think any of the big names of CPython or Python has showed up on that tracker as yet. But why is "be different from CPython" such a valuable choice? CPython works. It's had many hours of dev time put into it. Problems have been identified and avoided. Throwing that out means throwing away a freely-given shoulder to stand on, in an Isaac Newton way.