Skip to main content

Python Tests

Publish Python 🐍 distribution 📦 to PyPI

Django Integrations

Tools for creating and managing multi-site integrations like API Keys and Tokens

Prerequisites

This pakcage makes use of Encrypted Fields that come form the django-fernet-fields packages. Make sure to checkout their documentation for any questions related to Field Encryption.

This package makes use of JSON fields so you'll need Download and install Postgresql. This will change with Django 3.1+ and the universal JSON field.

Installation

> pip install django-integration

For Developers

Make sure you run the following command to ensure you have all the requirements needed to us the develop example project:

pip install -e .[dev]

Then run the migration command inside the develop folder

./manage.py migrate

finally create a super user:

./manage.py createsuperuser

Example

In the develop django project you will find a core application that has three Forms each with its view to show case how to use the Credential Model in the integration package.

For example you have a ZoomForm to present the user with the fields Zoom gives to use their API with you project. The ZoomForm is responsible for presenting and validating the fields and linking it to the credentials Model just like a normal ModelForm would.

class ZoomForm(forms.ModelForm):

    class Meta:
        model = Credential
        fields = ['public_key', 'private_key']
        labels = {
            'public_key': "Zoom Key",
            'private_key': "Zoom Secret"
        }

    def __init__(self, *args, **kwargs):
        super().__init__(*args, **kwargs)
        self.fields['public_key'].required = True
        self.fields['private_key'].required = True

It is in the view where it creates a Credential Model instance form the form submitted and saved. If you need to add additional fields or logic you can do it here, for example settting the site field in the Credential Model.

class ZoomFormView(FormView):
    template_name = "core/form.html"
    form_class = ZoomForm
    success_url = reverse_lazy('integration-list')

    def form_valid(self, form):
        zoom = form.save(commit=False)
        zoom.name = 'Zoom Integration'
        zoom.site = Site.objects.get_current()
        zoom.save()
        return super().form_valid(form)

Metadata

Release files for django-integrations 0.5.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for django-integrations 0.5.0
File Size Uploaded
django_integrations-0.5.0.tar.gz 6.8 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for django-integrations 0.5.0
File Interpreter ABI Platform
django_integrations-0.5.0-py3-none-any.whl Python 3 none any Details

Total release size: 16.2 kB

Release files / django_integrations-0.5.0.tar.gz

Download URL django_integrations-0.5.0.tar.gz
Size 6.8 kB
Tags Source
SHA-256 checksum
How to use checksums
c503b1a167cc786ae23010218462d43e9addfa4b515daf1c3cf63c1dcc8f9afe
BLAKE2b-256 checksum
How to use checksums
e79b26e41ed1a845eb0f24fed431ec281613eb6ff4d8df6941372f8ccb03da4d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

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 Apr 27, 2026.

Transparency log

Release files / django_integrations-0.5.0-py3-none-any.whl

Download URL django_integrations-0.5.0-py3-none-any.whl
Size 9.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
992c5f76ae8b1d132ec12dfa42a9e14f483c3891c4dffaf9892e026455207bbe
BLAKE2b-256 checksum
How to use checksums
863d85f6cf6ce9b1beebf6d275c9e30c02bc8f9770e9d3eebd0b6c6f356f3ec1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

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 Apr 27, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.5.0 This release

2 release files

0.4.0

2 release files

0.2.0

2 release files

0.1.4

2 release files

0.1.3

2 release files

0.1.2

2 release files

0.1.1

2 release files

0.1.0

1 release file

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page