toga-positron
A Briefcase bootstrap for setting up Toga apps whose GUI generated by displaying web content. (i.e., Electron-like apps... but more positive, because they're using Python!)
Usage
Create a fresh virtual environment, then install toga-positron. This will install Briefcase, plus the Positron bootstrap. You can then use the Briefcase wizard to create a new Toga app:
$ python -m venv venv
$ source venv/bin/activate
(venv) $ pip install toga-positron
(venv) $ briefcase new
This will ask you a number of questions about the app you want to generate, such as the app's name, the authors name, and the project license. You'll then be asked which GUI framework you want to use:
-- GUI framework -------------------------------------------------------------
What GUI toolkit do you want to use for this project?
Additional GUI bootstraps are available from the community.
Check them out at https://beeware.org/bee/briefcase-bootstraps
1) Toga
2) PySide6 (does not support iOS/Android/Web deployment)
3) Pygame (does not support iOS/Android/Web deployment)
4) Console (does not support iOS/Android/Web deployment)
5) Toga Positron (Django server) (does not support Web deployment)
6) Toga Positron (Site-specific browser) (does not support Web deployment)
7) Toga Positron (Static server) (does not support Web deployment)
8) None
GUI framework [1]:
This provides 3 options for a Toga Positron-based app:
Django server
An app that runs a Django web server in a background thread, and points the app's web browser at the URL for that server. Some additional files (such as urls.py and settings.py) will be generated by the app template.
The Django site that is generated is essentially identical to the default Django project created by startproject, with some minor modifications to set app-specific paths and ensure that static files will be served.
If you select this option, you will be asked for the initial path that you want to display in the app window. The default value is /admin/, which will cause the Django Admin login page (i.e., http://127.0.0.1/admin/) to be the initial URL loaded by the app, but you can choose any other URL you want (including / to serve the root URL of the Django site).
To run Django management commands, use::
(venv) PYTHONPATH=src python src/manage.py <command> <args...>
The Django app will run on a SQLite3 database, stored in the user's data directory (the location of this directory is platform specific). This database file will be created if it doesn't exist, and migrations will be run on every app start.
If you need to start the database with some initial content (e.g., an initial user login) you can use manage.py to create an initial database file. If there is a db.sqlite3 in the src/<app name>/resources folder when the app starts, and the user doesn't already have a db.sqlite3 file in their app data folder, the initial database file will be copied into the user's data folder as a starting point.
To create an initial database, use manage.py - e.g.,:
(venv) PYTHONPATH=src python src/manage.py migrate
(venv) PYTHONPATH=src python src/manage.py createsuperuser
This will create an initial db.sqlite3 file with a superuser account. All users of the app will have this superuser account in their database.
Site-specific browser
An app that behaves as a web browser that displays a single, externally served URL.
If you select this option, you will be asked for the URL that you want to display in the app window. For example, if you nominate https://github.com as the site URL, you will generate an app that, when started, loads the GitHub homepage.
Static server
An app that runs a simple HTTP server on a background thread, and points the app's web browser at the URL for that server. This is suitable for serving simple static HTML and CSS content. The app will serve the contents of the app's resources folder (i.e., src/<app name>/resources) as the root URL. A placeholder index.html file is generated in the resources folder as part of the template.
Community
Toga Positron is part of the BeeWare suite. You can talk to the community through:
We foster a welcoming and respectful community as described in our BeeWare Community Code of Conduct
Contributing
If you experience problems with Toga, log them on GitHub.
If you'd like to contribute to Toga development, our contribution guide details how to set up a development environment, and other requirements we have as part of our contribution process.
Metadata
Release files for toga-positron 0.5.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| toga_positron-0.5.7.tar.gz | 14.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| toga_positron-0.5.7-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 32.3 kB
Release files / toga_positron-0.5.7.tar.gz
| Download URL | toga_positron-0.5.7.tar.gz |
|---|---|
| Size | 14.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
06a31a39a26236076010e61c25cc097c28c90d057cf517b4ddfc8336ed8d73cd
|
|
BLAKE2b-256 checksum How to use checksums |
36ad43eb20fc71b5f130a0c42a109eeee0bb79ee61eb8a7628880065dfe55959
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 1, 2026.
Transparency logRelease files / toga_positron-0.5.7-py3-none-any.whl
| Download URL | toga_positron-0.5.7-py3-none-any.whl |
|---|---|
| Size | 18.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3825f3bd7d2e76f01f2540d19d61b658cc3586080c995c6a56fad563fe52ffd3
|
|
BLAKE2b-256 checksum How to use checksums |
5edaa12213d2099f5cdfcddd435c244333d0ff85551fff419fd73c70673432af
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 1, 2026.
Transparency log