sales_menu
The simple menu for Django.
Quickstart
Install sales_menu:
pip install sales_menu
Add sales_menu to your INSTALLED_APPS list in your settings.
sales_menu requires that the request object be available in the context when you call the {% menu %} template tag. This means that you need to ensure that your TEMPLATE_CONTEXT_PROCESSORS setting includes django.core.context_processors.request, which it doesn’t by default.
And use in template:
{% menu_tags %}
{% menu %}
{% for item in menu %}
<p>{{ item.text }}
{% if menu_item in selected_menu_path %}
— selected
{% endif %}
</p>
{% for child in item.children %}
<p>— {{ child.text }}</p>
{% endfor %}
{% endfor %}
Features
TODO
History
0.0.1 (2014-04-09)
First release on PyPI.
0.1.0 (2014-09-30)
Fixed outdated requirements
Added requires.io badge
Run test on Django 1.7
0.1.1 (2014-09-30)
Fixed run on Django 1.4
1 maintainer
Metadata
1 maintainer
Release files for sales_menu 0.1.1
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 | |
|---|---|---|---|---|
| sales_menu-0.1.1.tar.gz | 6.6 kB | Without provenance | Details |
Security for sales_menu 0.1.1
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.
