[issue33876] doc Mention the MicroPython implementation in Introduction

Petr Viktorin added the comment: > I didn't add Cython because it's not clear to me if it's useful for creating > extension modules in a pythonesque language, or if it's also useful by it's > own. Cython only makes extensions for CPython, and uses CPython's runtime. But it does have its own

[issue33876] doc Mention the MicroPython implementation in Introduction

Andrés Delfino added the comment: I have updated the PR with a FAQ that mentions all implementations mentioned here, except Cython and Stackless Python. I added RapydScript as it's used by VPython for Web visualization, in the category of client-side scripting pythonesque languages/implementa

[issue33876] doc Mention the MicroPython implementation in Introduction

Carol Willing added the comment: I think your suggestion for Brython and Skulpt is excellent. I believe that it's important to point out that Python can be used client-side, and both your suggestions have been around for a while, are stable, and often used in large courses such as OpenEdX.

[issue33876] doc Mention the MicroPython implementation in Introduction

Andrés Delfino added the comment: What do you think about also mentioning Skulpt and Brython? On one hand, they -like MicroPython/CirtcuitPython- cover a focus no other implementation does (and a special one: client side Web scripting); but on the other hand, we shouldn't make space for every

[issue33876] doc Mention the MicroPython implementation in Introduction

Carol Willing added the comment: Thanks Raymond :-) The FAQ seems like a good place to share. Cython would be a nice addition and perhaps IPython too. -- ___ Python tracker

[issue33876] doc Mention the MicroPython implementation in Introduction

Andrés Delfino added the comment: Sorry, I didn't knew that :) I'll update the PR adding an entry in the FAQ. With "CPython" in "pythonesque implementation like MicroPython, CircuitPython, CPython" did you mean Cython? -- ___ Python tracker

[issue33876] doc Mention the MicroPython implementation in Introduction

Raymond Hettinger added the comment: Addenda: Somewhere in the annals of our history this was discussed before (perhaps dating back to Stackless Python). -- ___ Python tracker _

[issue33876] doc Mention the MicroPython implementation in Introduction

Raymond Hettinger added the comment: IIRC, Guido recognized only PyPy, Jython, and IronPython as alternate conforming implementations. A number of other projects were python-like but were also going off in their own directions not subject to his pronouncements. MicroPython is a pretty cool

[issue33876] doc Mention the MicroPython implementation in Introduction

Carol Willing added the comment: A reasonable suggestion. Let's make sure that we mention CircuitPython as well. -- nosy: +willingc ___ Python tracker ___

[issue33876] doc Mention the MicroPython implementation in Introduction

Change by Andrés Delfino : -- keywords: +patch pull_requests: +7349 stage: -> patch review ___ Python tracker ___ ___ Python-bugs-li

[issue33876] doc Mention the MicroPython implementation in Introduction

New submission from Andrés Delfino : IMHO, mentioning MicroPython is a plus because it's a mature project with a focus not covered by any of the other mentioned implementations. PR adds the mention. -- assignee: docs@python components: Documentation messages: 319700 nosy: adelfino, doc