This library allows you to load initial Fixtures automagically after the South migrate your Model
Installation
The latest stable version of autoload-fixtures can always be installed or updated to via pip (prefered) or easy_install:
$ pip install --upgrade django-autoload-fixturesAlternatively:
$ easy_install --upgrade django-autoload-fixturesUsage
Set the new app inside your INSTALLED_APPS from settings.py:
INSTALLED_APPS = (
...
'autoload_fixtures',
...
)Create the model_name.json files inside your project/app_name/fixtures/ dir, if you already have data inside your models and want to use:
$ python manage.py dumpdata app_name.model_name --natural --indent=4 >> app_name/fixtures/model_name.jsonMigrate your project, using the south command:
$ python manage.py migrate1 maintainer
Metadata
1 maintainer
Release files for django-autoload-fixtures 0.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 | |
|---|---|---|---|---|
| django-autoload-fixtures-0.2.tar.gz | 2.1 kB | Without provenance | Details |
Release files / django-autoload-fixtures-0.2.tar.gz
| Download URL | django-autoload-fixtures-0.2.tar.gz |
|---|---|
| Size | 2.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2b176fc002eedf85e8b7d6bbc2b41f150b830296f832cde6cf10a14d1fb2c67f
|
|
BLAKE2b-256 checksum How to use checksums |
539dd5e1171ceba546760b3e06f7ccebc4479606a912346e2cb074cc3133d862
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-autoload-fixtures 0.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.
