mirror of
https://github.com/zulip/zulip.git
synced 2025-11-04 22:13:26 +00:00
a099e698e2
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.
35 lines
766 B
Python
Executable File
35 lines
766 B
Python
Executable File
#!/usr/bin/env python3
|
|
|
|
from pygments.lexers import get_all_lexers
|
|
import json
|
|
import os
|
|
|
|
ZULIP_PATH = os.path.join(os.path.dirname(os.path.abspath(__file__)), '../../')
|
|
DATA_PATH = os.path.join(ZULIP_PATH, 'tools', 'setup', 'lang.json')
|
|
JS_PATH = os.path.join(ZULIP_PATH, 'static', 'generated', 'pygments_data.js')
|
|
|
|
with open(DATA_PATH) as f:
|
|
langs = json.load(f)
|
|
|
|
lexers = get_all_lexers()
|
|
for lexer in lexers:
|
|
for name in lexer[1]:
|
|
if name not in langs:
|
|
langs[name] = 0
|
|
|
|
template = '''var pygments_data = (function () {
|
|
|
|
var exports = {};
|
|
|
|
exports.langs = %s;
|
|
|
|
return exports;
|
|
|
|
}());
|
|
if (typeof module !== 'undefined') {
|
|
module.exports = pygments_data;
|
|
}''' % json.dumps(langs)
|
|
|
|
with open(JS_PATH, 'w') as f:
|
|
f.write(template)
|