3 ms·
> Why didn't the Python committee opt for a compiled system (like PyPy) Because compilers are complicated and have trade-offs. > and had to break backward com
by chrisseaton 5y ago
> Why didn't the Python committee opt for a compiled system (like PyPy)
Because compilers are complicated and have trade-offs.
> and had to break backward compatibility anyway
A compiler shouldn't break backward compatibility.
- eatonphil 5y ago> A compiler shouldn't break backward compatibility. I don't understand what you mean by this in context (since they introduced a new language in python3).
- chrisseaton 5y agoThey asked why didn't Python 3 introduce a compiler when they were able to break backwards compatibility. That question doesn't make sense, because a compiler shouldn't have any impact on your compatibility. They can introduce a compiler without breaking compatibility, so they don't need to do it with a new language version.
- eatonphil 5y agoOh I see what you mean, I misread the sentence. Switching between language backends has nothing to do with compatibility. Yup makes sense. They can swap implementations at any time.
- amelius 5y agoThe point really is that PyPy has some compatibility issues with the C api I think mostly because of the garbage collector. This has less to do with whether you compile or interpret bytecode, yes.