Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Stupid somewhat on topic question: how are we supposed to understand the parallel existence of python 2.x and python 3?


2.6 is a bridge to 3.0 -- it implemented some 3.0 things, but kept a lot of backward compatibility. If a project can't convert to 3.0, they could convert to 2.6, which would then make the eventual 3.0/3.1 migration easier.


Python 3 made some critical changes that are incompatible with older 2.x code.

I believe 2.6 is meant to make it easier to transition from older python code to version 3.


From the release notes: This is the second bugfix release of the Python 2.6 series. Python 2.6 is now in bugfix-only mode; no new features are being added. Dozens of bugs that were reported since the release of 2.6.1 have been fixed.




Consider applying for YC's Winter 2027 batch! Applications are open till November 2.

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

Search: