Commit cb307bf0 authored by Lukas Fleischer's avatar Lukas Fleischer
Browse files

Do not hardcode path to the Python interpreter



Use `/usr/bin/env python3` instead of `/usr/bin/python3` in the shebang
of Python scripts. This adds support for non-standard Python interpreter
paths such as the paths used in virtualenv environments.

Signed-off-by: Lukas Fleischer's avatarLukas Fleischer <lfleischer@archlinux.org>
parent 2d2bef35
#!/usr/bin/python3
#!/usr/bin/env python3
import os
import shlex
......
#!/usr/bin/python3
#!/usr/bin/env python3
import os
import re
......
#!/usr/bin/python3
#!/usr/bin/env python3
import os
import pygit2
......
#!/usr/bin/python3
#!/usr/bin/env python3
import pyalpm
import re
......
#!/usr/bin/python3
#!/usr/bin/env python3
import datetime
import gzip
......
#!/usr/bin/python3
#!/usr/bin/env python3
import email.mime.text
import subprocess
......
#!/usr/bin/python3
#!/usr/bin/env python3
import time
......
#!/usr/bin/python3
#!/usr/bin/env python3
import time
......
#!/usr/bin/python3
#!/usr/bin/env python3
import re
import pygit2
......
#!/usr/bin/python3
#!/usr/bin/env python3
import subprocess
import time
......
#!/usr/bin/python3
#!/usr/bin/env python3
"""
usage: gendummydata.py outputfilename.sql
"""
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment