This release is a pre-release and may not be stable for production use.
With django-dbpreferences you can store some app preferences into the database.
A django app defines a form with initial values. The form cleaned data dict would
be stored serialized into the database. The app can easy get the current preference
dict and the user can easy edit the values in the django admin panel.
h2. history
* v0.3.4
** Bugfix if help_text contains non ascii characters and html code
* v0.3.3
** validate preferences with model validation
** clean preferences in get_preferences()
* v0.3.2
** some bugfixes
* v0.3.1
** Bugfix if DictField can be null / DictFormField(required=False)
* v0.3.0
** separate field stuff from models.py into fields.py, so its usable in other projects, too.
** Use own dict class for serialize/deserialize
** Update unittest for new django admin url prefix
* v0.2.0
** Add UserSettings, see: http://www.jensdiemer.de/_command/118/blog/detail/64/ (de)
* v0.1.0
** first version cut out from PyLucid CMS - http://www.pylucid.org
h2. pip upgrade
To do a pip upgrade in a virtual environment, run this:
pre. ~$ cd /YourVirtualEnv/bin
~/YourVirtualEnv/bin$ source activate
(YourVirtualEnv)~/YourVirtualEnv/bin$ pip install --upgrade --verbose --editable=git+git://github.com/jedie/django-dbpreferences.git#egg=django-dbpreferences
The example used git readonly clone url. If you use subversion do this:
pre. (YourVirtualEnv)~/YourVirtualEnv/bin$ pip install --upgrade --verbose --editable=http://svn.github.com/jedie/django-dbpreferences.git#egg=django-dbpreferences
If you have git write access, use this:
pre. (YourVirtualEnv)~/YourVirtualEnv/bin$ pip install --upgrade --verbose --editable=git+git@github.com:jedie/django-dbpreferences.git#egg=django-dbpreferences
h2. fast repo update
To made a fast repository update, you can run this simple shell script:
pre. ~$ cd /path/to/django-dbpreferences
/path/to/django-dbpreferences$ ./update.sh
the update script runs "git pull origin master" or "svn update".
h2. links
* homepage: http://code.google.com/p/django-dbpreferences/
* Sourcecode: http://github.com/jedie/django-dbpreferences
* PyPi: http://pypi.python.org/pypi/django-dbpreferences/
Metadata
Release files for django-dbpreferences 0.3.4.git-c57b020
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-dbpreferences-0.3.4.git-c57b020.tar.gz | 18.8 kB | Without provenance | Details for django-dbpreferences-0.3.4.git-c57b020.tar.gz |
Release files / django-dbpreferences-0.3.4.git-c57b020.tar.gz
| Download URL | django-dbpreferences-0.3.4.git-c57b020.tar.gz |
|---|---|
| Size | 18.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b2da1c04a3d4e17f3ad99813740085e8e38e36d884da5bdd63a48cc2ca28812a
|
|
BLAKE2b-256 checksum How to use checksums |
02c55971736947b73751578192c4f03ce3954d49c2a8880b82eabcc475b006e7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-dbpreferences 0.3.4.git-c57b020
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.