Grumpy: Go running Python

Re:Grumpy: Go running Python by orf on Wednesday January 04, 2017 @07:26PM (#13323568)

CPython is the spec (or really more the CPython test suite). Just like the Ruby MRI. It's a simple, plain interpreter without many frills, and to add or remove a feature you have to submit a PEP which goes through a specification process.

Python started as a one-man-band project and of course didn't have a specification.

[ Parent | on HN ]

Re:Grumpy: Go running Python by lomnakkus on Wednesday January 04, 2017 @07:42PM (#13323661)

Yes, but that's what the PP was arguing wasn't the case (by linking to a "spec"). I'm not sure why you're restating the obvious (OPs position).

[ Parent | on HN ]

Re:Grumpy: Go running Python by madgar on Thursday January 05, 2017 @09:36AM (#13327363)

> Python started as a one-man-band project and of course didn't have a specification.

C started as a one-man-band project and of course does have a specification.

JavaScript started as a one-man-band project and of course does have a specification.

[ Parent | on HN ]

Re:Grumpy: Go running Python by orf on Thursday January 05, 2017 @10:12AM (#13327650)

C wasn't a one man band project (at least a two-man-band one at the start!) and neither was JavaScript. C also didn't have a formal specification for over 20 years (only an informal one) and JavaScript had a strong selection bias for interpreters that roughly conformed to the specification. But that didn't exactly help it, JS is/was notorious for differing implementations of browser APIs.

Each of them also has a strong need for a specification, as there are many differing compilers and interpreters. There are a few for Python but are specialized, the CPython interpreter is good enough for 90% of cases.

[ Parent | on HN ]