News for hackers. Stuff that matters.

A comment on Python Versions Used in Commercial Projects, 2016 Edition. Parent comment

Re:Python Versions Used in Commercial Projects, 2016 Edition by oneweekwonder on Friday November 11, 2016 @08:59AM (#12930634)
Am I incorrect in recalling that ArchLinux decided against this?

edit: seems to be the case[0]

[0]: https://wiki.archlinux.org/index.php/python#Python_2

[ Parent | on HN ]
Re:Python Versions Used in Commercial Projects, 2016 Edition by qznc on Friday November 11, 2016 @10:36AM (#12931528)
Read the next line in PEP 394 ;)

> however, end users should be aware that python refers to python3 on at least Arch Linux (that change is what prompted the creation of this PEP), so python should be used in the shebang line only for scripts that are source compatible with both Python 2 and 3.

[ Parent | on HN ]
Re:Python Versions Used in Commercial Projects, 2016 Edition by majewsky on Friday November 11, 2016 @09:41AM (#12930972)
Yes, which is why it is a staple of PKGBUILDs for Python software to do

  sed -i s/python/python3/ /all/the/things
[ Parent | on HN ]
Re:Python Versions Used in Commercial Projects, 2016 Edition by gsnedders on Friday November 11, 2016 @09:35AM (#12930921)
Before upstream CPython had any defined policy on the python symlink.
[ Parent | on HN ]