META EDC
Metformin treatment in Africa - META
py 3.12+ / DJ 5.2-6.0 using the Clinic EDC framework
This codebase is used for two randomized clinical trials:
META PHASE II:
(final deployed version 0.1.77)
Metformin Treatment for Diabetes Prevention in Africa: META Trial TASO, MRC/UVRI/LSHTM, NIMR – TZ and Liverpool School of Tropical Medicine (ISRCTN76157257) http://www.isrctn.com/ISRCTN76157257
META PHASE III:
(final deployed version 3.18.4) 02/10/2026
A randomised placebo-controlled double-blind phase III trial to determine the effects of metformin versus placebo on the incidence of diabetes in HIV-infected persons with pre-diabetes in Tanzania.
Liverpool School of Tropical Medicine
EDCTP grant number: RIA2018CO-2513
Trial registration: ISCRTN 77382043
https://ico.org.uk/ESDWebPages/Entry/Z4763134
See also https://github.com/clinicedc/edc
Installation
As of version 1.1.10, we are building and deploying with uv.
Here we assume you have your DB setup and already have your .env file.
First-time install
Assuming you are logged into the account myaccount:
mkdir -p ~/.etc/meta && \
mkdir ~/edc && \
cd ~/edc && \
uv venv && \
uv pip install -U meta-edc==3.18.3 && \
wget https://raw.githubusercontent.com/meta-trial/meta-edc/3.18.3/manage.py && \
uv pip freeze | grep meta-edcCopy your .env file to ~/.etc.
Place this at or near the end of your .bashrc:
# >>> EDC using uv >>>
export DJANGO_SETTINGS_MODULE=meta_edc.settings.uat
export META_PHASE=3
export DJANGO_BASE_DIR=/home/myaccount/edc
export DJANGO_ENV_DIR=/home/myaccount/.etc/
cd ~/edc
source .venv/bin/activate
export PATH="/home/myaccount/edc:$PATH"
# <<< EDC using uv <<<Source .bashrc and run manage.py check.
source ~/.bashrc && \
cd ~/edc && \
python manage.py checkIf all is OK, run migrate:
Explicitly specify the settings file when using migrate.
live: --settings=meta_edc.settings.live
uat: --settings=meta_edc.settings.uat
debug: --settings=meta_edc.settings.debug
cd ~/edc && \
python manage.py migrate --settings=meta_edc.settings.liveUpdate an existing install
From the above example:
cd ~/edc && \
uv venv --clear && \
uv pip install -U meta-edc==3.18.3 && \
wget -O manage.py https://raw.githubusercontent.com/meta-trial/meta-edc/1.1.10/manage.py && \
uv pip freeze | grep meta-edc && \
python manage.py checkIf all is OK, run migrate
cd ~/edc && \
python manage.py migrate --settings=meta_edc.settings.live2 maintainers
Metadata
2 maintainers
Release files for meta-edc 3.18.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| meta_edc-3.18.4.tar.gz | 1.8 MB | Without provenance | Details for meta_edc-3.18.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| meta_edc-3.18.4-py3-none-any.whl | Python 3 | none | any | Details for meta_edc-3.18.4-py3-none-any.whl |
Total release size: 4.1 MB
Release files / meta_edc-3.18.4.tar.gz
| Download URL | meta_edc-3.18.4.tar.gz |
|---|---|
| Size | 1.8 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c68c876270ebb15839f98ebfaada38a6d3683d909f1ced93dd7855493c5de5b7
|
|
BLAKE2b-256 checksum How to use checksums |
12850da259bcd9a69dc4fd3541854c7b4ba28fd4ce3f236047101253010400b8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.22 {"installer":{"name":"uv","version":"0.12.22","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / meta_edc-3.18.4-py3-none-any.whl
| Download URL | meta_edc-3.18.4-py3-none-any.whl |
|---|---|
| Size | 2.4 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5bb8ba15bed42d2894b883101c37eed82f32a25d3b40afa1a1263b2b2fb0f9a0
|
|
BLAKE2b-256 checksum How to use checksums |
42c008240ce56547b51b01e9255f309383c770123c07436c41c877e5e10d64be
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.22 {"installer":{"name":"uv","version":"0.12.22","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for meta-edc 3.18.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
