system-config

History

Ian Wienand c2c0edfae4 gitea-git-repos: remove #!/usr/bin/env python A change in Ansible 6, discussed at [1], highlights that Ansible is using the #! line to determine using it's own heuristics the interpreter to use to run the file, rather than the more common idea that this file is being interpreted by the kernel. The best solution seems to be to have no interpreter line, which is done here. To avoid confusion this removes the executable bit; if you want to run it manually you should run it under the python binary as an argument. I couldn't find any other instances of this same behaviour in system-config. [1] https://github.com/ansible/ansible/issues/78809 [1] `9142be2f6c` [2] `9e22cfdb0f` Change-Id: I1d37e485a877982c72fa19acad907b682858c15b	2022-11-23 08:26:28 +11:00
..
__init__.py	Translate gitea project creation to python	2019-07-11 08:21:35 -04:00
gitea_create_repos.py	gitea-git-repos: remove #!/usr/bin/env python	2022-11-23 08:26:28 +11:00

gitea-git-repos: remove #!/usr/bin/env python

A change in Ansible 6, discussed at [1], highlights that Ansible is
using the #! line to determine using it's own heuristics the
interpreter to use to run the file, rather than the more common idea
that this file is being interpreted by the kernel.

The best solution seems to be to have no interpreter line, which is
done here.

To avoid confusion this removes the executable bit; if you want to run
it manually you should run it under the python binary as an argument.

I couldn't find any other instances of this same behaviour in
system-config.

[1] https://github.com/ansible/ansible/issues/78809

[1] 9142be2f6c
[2] 9e22cfdb0f

Change-Id: I1d37e485a877982c72fa19acad907b682858c15b

2022-11-23 08:26:28 +11:00

__init__.py Translate gitea project creation to python 2019-07-11 08:21:35 -04:00

gitea_create_repos.py gitea-git-repos: remove #!/usr/bin/env python 2022-11-23 08:26:28 +11:00