Re:Cargo-style dependency management for C, C++ and other la...
by int_19h on Wednesday October 21, 2020 @08:52AM
(#24847306)
Not quite - CPython docs specifically say that some things are implementation-specific, and that other implementations are free to do them differently. For example, there's no guarantee of refcounting, and portable Python code has to assume that implicit cleanup is non-deterministic (which is observable with __del__).
The problem, rather, is that coders tend to ignore this, and write code that only works on CPython.
Re:Cargo-style dependency management for C, C++ and other la...
by afiori on Wednesday October 21, 2020 @11:22AM
(#24848708)
This is what I meant as the advantage of multiple implementations, by "CPython does whatever it wants" I meant that the power dynamics are almost exclusively in favour of CPython
My understanding is that mostly CPython does whatever it wants and the other follows, but it is still better than a single implementation where the boundary between bug and spec would be nebulous.