Django-sticky-files
An application that solves a problem, when you need to save form’s file field values between page reloads (including form validation errors).
Currently in development.
Installation
Install an application:
pip install django-sticky-files
Then add sticky_files to INSTALLED_APPS.
Include urls:
url(r'^sticky-images/', include('sticky_files.urls', namespace='sticky_files')),
Usage
There are four model fields that implement sticky files behaviour:
from django.db import models
from sticky_files import fields
from sticky_files.models import FileBase
class SomeImage(FileBase):
pass
class SomeFile(FileBase):
pass
class SomeModel(models.Model):
main_image = fields.StickyImageField(
'app.SomeImage',
related_name='+'
)
images = fields.ManyStickyImageField(
'app.SomeImage',
max_objects=4,
related_name='galleries_images',
)
file = fields.StickyFileField(
'app.SomeFile',
related_name='+'
)
files = fields.ManyStickyFileField(
'app.SomeFile',
max_objects=4,
related_name='galleries_files',
)
It looks like this:
Project is in development, so there are no documentation and tests yet.
Metadata
Release files for django-sticky-files 0.3.2
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-sticky-files-0.3.2.tar.gz | 1.0 MB | Without provenance | Details for django-sticky-files-0.3.2.tar.gz |
Release files / django-sticky-files-0.3.2.tar.gz
| Download URL | django-sticky-files-0.3.2.tar.gz |
|---|---|
| Size | 1.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cf441cbacad35ef4d0dab89e14a74ec0c1f137369a2c308fc350b36648d4f279
|
|
BLAKE2b-256 checksum How to use checksums |
4fc2b5868cbee3d9880cedf532c1b7d8f3c63c720fe4f0ab9ca2d8cdf1d9b3ad
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-sticky-files 0.3.2
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.