Hacker News new | past | comments | ask | show | jobs | submit login

There won't be breaking changes from 3.3->3.5, so the code changes are the same either way. I guess skipping a release saves the effort of making the release/prioritizing things that appeared in 3.4.



Doing a 3.4 and even possibly a 3.5 release could be a waste of time. I think PyPy should head cpython off at the pass and release a 3.7


You can implement Your Own languages on pypy so make it 4 :)

Breaking changes I would include would be : remove all the deprecated bits of subprocess or replace it entirely, remove the zip, ftp and other modules in favour of virtual filesystems with a consistent api and finally try and make all the APIs symmetrical (e.g. open always paired with close, push with pop etc).

But then I am too lazy :)




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: