using Docker. 2. If you are not going to change Weblate code, but want to avoid Docker install in virtual env, see Installing in a virtualenv. 3. If you want to develop and/or change Weblate code, grab installation locally on your device to find out if Weblate is for you, you can install it using a virtual environment for Python 2, a simple (and slow!) SQLite database, and the lightweight Django development translatable contents to your test installation. You can stop the test server with Ctrl+C, and leave the virtual environment with deactivate. If you want to resume testing later, you need to repeat the steps 4

using Docker. 2. If you are not going to change Weblate code, but want to avoid Docker install in virtual env, see Installing in a virtualenv. 3. If you want to develop and/or change Weblate code, grab installation locally on your device to find out if Weblate is for you, you can install it using a virtual environment for Python 2, a simple (and slow!) SQLite database, and the lightweight Django development translatable contents to your test installation. You can stop the test server with Ctrl+C, and leave the virtual environment with deactivate. If you want to resume testing later, you need to repeat the steps 4

using Docker. 2. If you are not going to change Weblate code, but want to avoid Docker install in virtual env, see Installing in a virtualenv. 3. If you want to develop and/or change Weblate code, grab installation locally on your device to find out if Weblate is for you, you can install it using a virtual environment for Python 2, a simple (and slow!) SQLite database, and the lightweight Django development translatable contents to your test installation. You can stop the test server with Ctrl+C, and leave the virtual environment with deactivate. If you want to resume testing later, you need to repeat the steps 4

using Docker. 2. If you are not going to change Weblate code, but want to avoid Docker install in virtual env, see Installing in a virtualenv. 3. If you want to develop and/or change Weblate code, grab installation locally on your device to find out if Weblate is for you, you can install it using a virtual environment for Python 2, a simple (and slow!) SQLite database, and the lightweight Django development guide Weblate Documentation, Release 3.4 You can stop the test server with Ctrl+C, and leave the virtual environment with deactivate. If you want to resume testing later, you need to repeat the steps 4

installation locally on your device to find out if Weblate is for you, you can install it using a virtual environment for Python 3, a simple (and slow!) SQLite database, and the lightweight Django development weblate command, see Management commands. You can stop the test server with Ctrl+C, and leave the virtual environment with deactivate. If you want to resume testing later, you need to repeat steps 4, 8 and by invoking the script ./scripts/generate-locales. 2. Install all required dependencies into an virtual env (also see Software requirements): virtualenv --python=python3 .venv . .venv/bin/activate pip

installation locally on your device to find out if Weblate is for you, you can install it using a virtual environment for Python 3, a simple (and slow!) SQLite database, and the lightweight Django development weblate command, see Management commands. You can stop the test server with Ctrl+C, and leave the virtual environment with deactivate. If you want to resume testing later, you need to repeat steps 4, 8 and by invoking the script ./scripts/generate-locales. 2. Install all required dependencies into an virtual env (also see So�ware requirements): virtualenv --python=python3 .venv . .venv/bin/activate pip

installation locally on your device to find out if Weblate is for you, you can install it using a virtual environment for Python 3, a simple (and slow!) SQLite database, and the lightweight Django development weblate command, see Management commands. You can stop the test server with Ctrl+C, and leave the virtual environment with deactivate. If you want to resume testing later, you need to repeat steps 4, 8 and by invoking the script ./scripts/generate-locales. 2. Install all required dependencies into an virtual env (also see Software requirements): virtualenv --python=python3 .venv . .venv/bin/activate pip

using Docker. 2. If you are not going to change Weblate code, but want to avoid Docker install in virtual env, see Installing in a virtualenv. 3. If you want to develop and/or change Weblate code, grab installation locally on your device to find out if Weblate is for you, you can install it using a virtual environment for Python 2, a simple (and slow!) SQLite database, and the lightweight Django development translatable contents to your test installation. You can stop the test server with Ctrl+C, and leave the virtual environment with deactivate. If you want to resume testing later, you need to repeat the steps 4

using Docker. 2. If you are not going to change Weblate code, but want to avoid Docker install in virtual env, see Installing in a virtualenv. 3. If you want to develop and/or change Weblate code, grab installation locally on your device to find out if Weblate is for you, you can install it using a virtual environment for Python 2, a simple (and slow!) SQLite database, and the lightweight Django development translatable contents to your test installation. You can stop the test server with Ctrl+C, and leave the virtual environment with deactivate. If you want to resume testing later, you need to repeat the steps 4

using Docker. 2. If you are not going to change Weblate code, but want to avoid Docker install in virtual env, see Installing in a virtualenv. 3. If you want to develop and/or change Weblate code, grab installation locally on your device to find out if Weblate is for you, you can install it using a virtual environment for Python 2, a simple (and slow!) SQLite database, and the lightweight Django development translatable contents to your test installation. You can stop the test server with Ctrl+C, and leave the virtual environment with deactivate. If you want to resume testing later, you need to repeat the steps 4