*.py: use proper '#!/usr/bin/env' shebang

Using hard-coded paths in shebang is a bad idea, because on different
systems Python interpreter can be installed in different places. See:

https://mail.python.org/pipermail/tutor/2007-June/054816.html

Change-Id: Ib729ece0c95254dc2b235f90eb731681df955bd1
This commit is contained in:
Vadim Yanitskiy 2018-09-29 15:56:59 +07:00
parent 354904a0a6
commit 022be433ad
4 changed files with 5 additions and 4 deletions

View File

@ -1,4 +1,4 @@
#!/usr/bin/python #!/usr/bin/env python2
# Python implementation of GSM 04.08 call state machine for use with # Python implementation of GSM 04.08 call state machine for use with
# OsmoNITB MNCC interface # OsmoNITB MNCC interface

View File

@ -1,4 +1,4 @@
#!/usr/bin/python #!/usr/bin/env python2
# Python interface to OsmoNITB MNCC (Mobile Network Call Control) # Python interface to OsmoNITB MNCC (Mobile Network Call Control)
# interface # interface

View File

@ -1,4 +1,4 @@
#!/usr/bin/python #!/usr/bin/env python2
# Python testing tool for establishing calls via the OsmoNITB MNCC # Python testing tool for establishing calls via the OsmoNITB MNCC
# interface. # interface.

View File

@ -1,4 +1,5 @@
#!/usr/bin/python #!/usr/bin/env python2
import logging import logging
import sys import sys