3 ms·
Why anyone would start a project exclusively supporting Python 2 six years after the release of Python 3 is beyond me. (GitHub lists the first commit in Nov 201
by y7 9y ago
Why anyone would start a project exclusively supporting Python 2 six years after the release of Python 3 is beyond me. (GitHub lists the first commit in Nov 2014).
- hashkb 9y agoI don't know the specifics (sort of watching, amuses, from the sidelines) but the 2/3 schism is still very real. I'm not fluent in Python at all, and so it seems I have to have both, and if `pip install` doesn't work then I `pip3 install`. That seems pretty broken to me.
- dkuntz2 9y ago`pip` is dictated by your OS, so you've probably got python2 set as your default python.
- int_19h 9y agoPython itself has established the convention that the "python" binary is always 2.x, and "python3" is 3.x. Even if Python 2 is not installed at all. This naturally translated to other tools.
- y7 9y agoI don't think this is necessarily true? It used to be, but I sometimes see "python" being Python 3 and "python2" being Python 2.
- int_19h 9y agoIt's a PEP. https://www.python.org/dev/peps/pep-0394/ https://www.python.org/dev/peps/pep-0394/ The long-term plan is to make "python" version-agnostic. But for the time being, it is acknowledged that compatibility with Py2 is too important to do it just yet.
- garaetjjte 9y agoArch Linux is significant exception.
- iogf 9y agovy started when python3 was sort of an experiment, i haven't had many people interested in it in the last four years so i decided to keep it on py2, i have python3 support planned it is coming soon.