py3: Switch almost all shebang lines to use `python3`.
This causes `upgrade-zulip-from-git`, as well as a no-option run of
`tools/build-release-tarball`, to produce a Zulip install running
Python 3, rather than Python 2. In particular this means that the
virtualenv we create, in which all application code runs, is Python 3.
One shebang line, on `zulip-ec2-configure-interfaces`, explicitly
keeps Python 2, and at least one external ops script, `wal-e`, also
still runs on Python 2. See discussion on the respective previous
commits that made those explicit. There may also be some other
third-party scripts we use, outside of this source tree and running
outside our virtualenv, that still run on Python 2.
2017-08-02 23:15:16 +02:00
|
|
|
#!/usr/bin/env python3
|
2017-01-26 09:57:16 +01:00
|
|
|
|
|
|
|
|
import os
|
|
|
|
|
import signal
|
|
|
|
|
import sys
|
|
|
|
|
|
2021-02-12 08:20:45 +01:00
|
|
|
os.chdir(os.path.join(os.path.dirname(__file__), ".."))
|
|
|
|
|
pid_file_path = os.path.join(os.path.join(os.getcwd(), "var/run/run_dev.pid"))
|
2017-01-26 09:57:16 +01:00
|
|
|
|
|
|
|
|
try:
|
2020-04-09 21:51:58 +02:00
|
|
|
with open(pid_file_path) as pid_file:
|
2017-01-26 09:57:16 +01:00
|
|
|
try:
|
|
|
|
|
pid = int(pid_file.read())
|
|
|
|
|
except ValueError:
|
2021-02-12 08:20:45 +01:00
|
|
|
print("PID value is not an integer!")
|
2017-01-26 09:57:16 +01:00
|
|
|
sys.exit(1)
|
|
|
|
|
except Exception as e:
|
|
|
|
|
print("PID file can't be opened!")
|
|
|
|
|
print(e)
|
|
|
|
|
sys.exit(1)
|
|
|
|
|
|
|
|
|
|
# Kill development server process group.
|
|
|
|
|
try:
|
|
|
|
|
os.killpg(pid, signal.SIGTERM)
|
|
|
|
|
except OSError as e:
|
|
|
|
|
print(e)
|
|
|
|
|
sys.exit(1)
|
|
|
|
|
|
|
|
|
|
print("Done")
|
