Django-briteverify
Helper for easy integration between django and briteverify.com service.
It supports Python2.6+, Django1.4+
Installation
$ pip install django-briteverify
Usage
In common case as you need is use BriteverifyFormMixin for your forms and specify a BRITEVERIFY_API_KEY:
# your_app/forms.py
from django import forms
from django_briteverify import BriteverifyFormMixin
class RegisterForm(BriteverifyFormMixin, forms.Form):
email = forms.EmailField()
Set BRITEVERIFY_API_KEY as environment variable:
$ export BRITEVERIFY_API_KEY='YOUR_API_KEY'
Or define it directly in settings
# settings.py
BRITEVERIFY_API_KEY = 'YOUR_API_KEY'
You can specify field name which be used as source for verifying:
class RegisterForm(BriteverifyFormMixin, forms.Form):
another_email = forms.EmailField()
EMAIL_FIELD_NAME = 'another_email'
Also you can override error messages which raised if validation didn’t pass:
class RegisterForm(BriteverifyFormMixin, forms.Form):
error_messages = {
'invalid_email': _('This is an invalid email address. '
'Maybe you mistyped?'),
'disposable_email': _('Please provide your real email address.')
}
Contributing
Fork the django-briteverify repo on GitHub.
Clone your fork locally:
$ git clone git@github.com:your_name_here/django-briteverify.git
Install your local copy into a virtualenv. Assuming you have virtualenvwrapper installed, this is how you set up your fork for local development:
$ mkvirtualenv django-briteverify
$ cd django-briteverify/
$ python setup.py develop
Create a branch for local development:
$ git checkout -b name-of-your-bugfix-or-feature
Now you can make your changes locally.
When you’re done making changes, check that your changes pass the tests, including testing other Python versions with tox:
$ pip install tox
$ tox
Commit your changes and push your branch to GitHub:
$ git add .
$ git commit -m "Your detailed description of your changes."
$ git push origin name-of-your-bugfix-or-feature
Submit a pull request through the GitHub website.
Metadata
Release files for django-briteverify 1.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-briteverify-1.0.tar.gz | 4.6 kB | Without provenance | Details for django-briteverify-1.0.tar.gz |
Release files / django-briteverify-1.0.tar.gz
| Download URL | django-briteverify-1.0.tar.gz |
|---|---|
| Size | 4.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d2b1b977403d210c30a0e8df5aad8b562f786b243bc96f836e4d772e5e03cb27
|
|
BLAKE2b-256 checksum How to use checksums |
abb02faf001450ff0fd1185293b97d1d9def8ee7296eac476df9537278051417
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-briteverify 1.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.