This release is a pre-release and may not be stable for production use.
Radiant-Wrapper
Radiant-Wrapper is a Docker image that allows you to generate APKs for Android. It's essentially a wrapper for python-for-android with all dependencies included. This tool has the ability to compile three kinds of projects:
- Static HTML - Projects with an index.html file
- Django Projects - Web applications built with Django
- Python Projects - Any Python project that implements a main.py file
Installation
Pull the Docker image that includes the Android NDK and SDK:
docker pull dunderlab/radiant_p4a
Then install the Python package to use the wrapper command:
pip install radiant-wrapper
Usage
The radiant_p4a command replaces the standard p4a command and runs it inside the Docker container:
radiant_p4a.py apk --arch arm64-v8a
Project Types
Static HTML
If your project contains an index.html file, Radiant-Wrapper will automatically create a main.py file that sets up a
simple HTTP server to serve your static files.
For a complete example of a static HTML project, see: https://github.com/dunderlab/radiant-html_template
Django Projects
If your project contains a Django application (identified by the presence of manage.py), Radiant-Wrapper will set up
the necessary environment to run your Django app on Android.
For a complete example of a Django project, see: https://github.com/dunderlab/radiant-django_template
Python Projects with main.py
If your project already has a main.py file, Radiant-Wrapper will use it directly to build your Android application.
GitHub Workflow for Automated APK Generation
A GitHub workflow is available to automate the APK generation process. When added to your repository, this workflow will automatically build an Android APK for your project on every push or when manually triggered. The workflow handles all project types (Static HTML, Django, and Python with main.py) and uploads the generated APK as an artifact.
To use this workflow, copy the radiant_wrapper.yml file to your repository's .github/workflows/ directory.
Software Versions Included in the Image
NDK_VERSION=r28c
SDK_VERSION=13114758_latest
JAVA_VERSION=jdk17-openjdk
NDKAPI=35
ANDROIDAPI=35
BUILDTOOL=35.0.0
P4A_VERSION=2024.1.21
CYTHON_VERSION=3.0.4
Metadata
Release files for radiant-wrapper 0.1a10
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| radiant_wrapper-0.1a10.tar.gz | 9.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| radiant_wrapper-0.1a10-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 17.7 kB
Release files / radiant_wrapper-0.1a10.tar.gz
| Download URL | radiant_wrapper-0.1a10.tar.gz |
|---|---|
| Size | 9.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f4ec1c6c2e81b3ec212535c21a94472343ec75eb119a1561d4b03aeaafe3e214
|
|
BLAKE2b-256 checksum How to use checksums |
cec8fa27498304d76009403b7a6306722a0837b818ca7bc00607171cc34b8909
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 31, 2025.
Transparency logRelease files / radiant_wrapper-0.1a10-py3-none-any.whl
| Download URL | radiant_wrapper-0.1a10-py3-none-any.whl |
|---|---|
| Size | 8.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2fe3ccd87e61d59046d32ddad49f970bde8c813366f920221a01fde7616c0d0b
|
|
BLAKE2b-256 checksum How to use checksums |
f0a3a9c597f07dfb9b7ec68b6573411c4a2146ba46f99f790a25793b4cbd5526
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 31, 2025.
Transparency log