Making Python 3 more attractive

Making Python 3 more attractive

I agree that mark/sweep collectors are not universally the best option, for reasons of memory overhead, non-determinism, complexity, and so forth.

However, in the case of python, I am more willing to make the claim that mark/sweep collection would be beneficial performance-wise. I am basing this on PyPy's previous experimentation with different collection algorithms, including reference counting (with cycle collection, as required by Python). Their experience has led them, like the JS folk, to use a single-generational mark/sweep collector.

Regardless of the performance, though, I doubt that cPython should ever switch, simply due to the benefits of a stable c api. The answer to lack of Python 3 adoption is unlikely to be further breaking changes... though I admit I have no idea what is the answer.