django-menus is an app that provides some useful template helpers for rendering and handling menus within django projects.
To use in in your django project, it needs to be installed:
$ pip install django-menus
And "menus" needs to be in your settings.INSTALLED_APPS.
Changes
1.1.2 - Python 3 support
1.1.1 - Pass through args and kwargs to the test function if it accepts them.
1.0.9 - Allow for adding classes, and buttons as menu items.
1.0.8 - Allow for absolute urls, ie, pointing to another server. We never try to validate these for permission to view, it is assumed the user can.
1.0.7 - Change how version number is stored. Include a new li-item.html template, and refactor how the template is found. Check func_code exists before accessing it. Refactor some of the handling of paths. Better handle quoting issues.
1.0.6 - Documentation fix only.
1.0.5 - Actually install all of the static media/templates.
1.0.4 - Don’t fail on install if README.md missing.
1.0.3 - Repackaged to include README.rst [Thanks to John Bazik jsb@cs.brown.edu]
Metadata
Release files for django-menus-py3 1.1.3
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-menus-py3-1.1.3.tar.gz | 7.9 kB | Without provenance | Details for django-menus-py3-1.1.3.tar.gz |
Security for django-menus-py3 1.1.3
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.