Using python2 instead of python in shebang lines

Archives Ansible Developer
1

Hi

Given that the requirement for the management host is py2.6+ and
PEP394[1] has been around some time now, would you consider using
'#!/usr/bin/env python2' instead of '#!/usr/bin/env python' in bin/*? I
can submit a PR for this.

Also see this Fedora ticket[2]

Cheers,
maykel

[1] http://legacy.python.org/dev/peps/pep-0394/
[2] https://fedorahosted.org/fpc/ticket/327

2

Doing this would break ansible on Mac, as Mac does not ship a python2 symlink/binary. I’m sure there are other OSes that it would cause issue with as well.

Ideally, if ansible eventually migrates to setuptools entrypoints, this would be solved without having to worry about system specific paths.

3

“Ideally, if ansible eventually migrates to setuptools entrypoints”

Can you share more specifics?

4

It's basically the changes from this PR:
https://github.com/ansible/ansible/pull/9401

Not quite sure if/how it would affect other distro-specific packaging.

5

I’m open to this, but we should just start it in the v2 subtree.

We’ll make a note to experiment later.