zulip/scripts/get-django-setting

#!/usr/bin/env python3
from __future__ import absolute_import
from __future__ import print_function

import os
import sys

BASE_DIR = os.path.dirname(os.path.dirname(os.path.abspath(__file__)))
sys.path.append(BASE_DIR)
import scripts.lib.setup_path_on_import

os.environ['DJANGO_SETTINGS_MODULE'] = 'zproject.settings'
from django.conf import settings

print(getattr(settings, sys.argv[1]))
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`
Add a simple script to fetch a setting out of Django. (imported from commit c0ebaf02108a930f0290d56bd666611e36ba28c0) 2013-10-24 01:51:06 +02:00			`from __future__ import absolute_import`
Apply Python 3 futurize transform libfuturize.fixes.fix_print_with_import Refer #256 2016-03-10 17:15:34 +01:00			`from __future__ import print_function`
Add a simple script to fetch a setting out of Django. (imported from commit c0ebaf02108a930f0290d56bd666611e36ba28c0) 2013-10-24 01:51:06 +02:00
			`import os`
			`import sys`

python: Add lint rule banning 'from os.path import'. This enforces our use of a consistent style in how we access Python modules; "from os.path import dirname" is a particularly popular abbreviation inconsistent with our style, and so it deserves a lint rule. Commit message and error text tweaked by tabbott. Fixes #6543. 2017-09-22 08:15:01 +02:00			`BASE_DIR = os.path.dirname(os.path.dirname(os.path.abspath(__file__)))`
Activate virtualenv in production Python code. The manage.py change effectively switches the Zulip production server to use the virtualenv, since all of our supervisord commands for the various Python services go through manage.py. Additionally, this migrates the production scripts and Nagios plugins to use the virtualenv as well. 2016-06-25 17:07:13 +02:00			`sys.path.append(BASE_DIR)`
			`import scripts.lib.setup_path_on_import`

Add a simple script to fetch a setting out of Django. (imported from commit c0ebaf02108a930f0290d56bd666611e36ba28c0) 2013-10-24 01:51:06 +02:00			`os.environ['DJANGO_SETTINGS_MODULE'] = 'zproject.settings'`
			`from django.conf import settings`

Apply Python 3 futurize transform libfuturize.fixes.fix_print_with_import Refer #256 2016-03-10 17:15:34 +01:00			`print(getattr(settings, sys.argv[1]))`