django-beta
django-beta is a simple application to help you capture pre-beta interest
with your sites.
By default django-beta only captures a user's email address, however you
can alternately set one of these two configuration options:
BETA_CAPTURE_FIRST = Truewill use a form and require the user to enter their first name and email address.BETA_CAPTURE_BOTH = Truewill use a form and require the user to enter their first name, last name, and email address.
Installation
Add beta to your INSTALLED_APPS and run migrations.
Add the following to your urls.py:
from django.urls import include, path
urlpatterns = [
path("beta/", include("beta.urls")),
]
Using the example templates provided in the code, create your customized beta signup templates.
Managers
The BetaSignup model has the following manager methods to help out:
BetaSignup.objects.contacted()
BetaSignup.objects.not_contacted()
BetaSignup.objects.registered()
BetaSignup.objects.not_registered()
Side Effects
django-beta listens for a signal on User creation and marks the
corresponding BetaSignup entry as registered.
Development
This project uses nox and just for testing and linting across a matrix of Python and Django versions.
just lint # run pre-commit / ruff via prek
just test # run the full nox test matrix
just test-latest # run against the latest Python and Django
TODO
- Admin views to show beta registrations over time
- Management commands to simplify emailing the interested users
2 maintainers
Metadata
2 maintainers
Release files for django-beta 0.3.0
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 |
|---|---|---|---|---|
| django_beta-0.3.0.tar.gz | 7.0 kB | Without provenance | Details for django_beta-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django_beta-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for django_beta-0.3.0-py3-none-any.whl |
Total release size: 15.0 kB
Release files / django_beta-0.3.0.tar.gz
| Download URL | django_beta-0.3.0.tar.gz |
|---|---|
| Size | 7.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
99c372f0447cdfdf60aeba71c60e3b45e29ce1f785d365283cc51053589648e2
|
|
BLAKE2b-256 checksum How to use checksums |
6a484733e9096992a71dde18ad255a389032fe2097a4f47d9c34161b0b8d3bae
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.0 {"installer":{"name":"uv","version":"0.13.0","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 / django_beta-0.3.0-py3-none-any.whl
| Download URL | django_beta-0.3.0-py3-none-any.whl |
|---|---|
| Size | 8.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3e09bc6d7673413a84114e52af825d84fdc82ed73ff4cfe35ef3de51b684e992
|
|
BLAKE2b-256 checksum How to use checksums |
a1e61f77161ae92036a90c5b3532957a527f5c421de52d5ac50c2a0ccc9a9a48
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.0 {"installer":{"name":"uv","version":"0.13.0","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 django-beta 0.3.0
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.
