On Sun, Feb 14, 2021 at 3:05 PM Christian Gollwitzer <aurio...@gmx.de> wrote:
> Am 14.02.21 um 11:12 schrieb Paul Rubin: > > Christian Gollwitzer <aurio...@gmx.de> writes: > >> He wants that neoGFX is scriptable in Python, but instead of linking > >> with CPython, he will write his own Python implementation instead, > >> because CPython is slow/not clean/ whatever. He doesn't seem to > >> understand that this is an enormous task on its own, because the > >> interesting part of a scripting language is the standard library with > >> many decade-years of work. > > > > I wonder how big an issue the stdlib really is. Lots of it is written > > in Python and can port to another interpreter. Lots more is CPython C > > API bindings to external C libraries (e.g. OpenSSL) so porting those > > would be a matter of rebinding those libraries to libffi in the cases > > where that hasn't been done already. > Hopefully CFFI, not libffi: https://cffi.readthedocs.io/en/latest/ I'm not saying that it is unfeasible or very difficult. I'm saying that > it is a lot of work It is. However, IronPython and Shedskin do not have a full Python standard library. I'd still call them "Python". -- https://mail.python.org/mailman/listinfo/python-list
