1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
|
%global _empty_manifest_terminate_build 0
Name: python-django-mustache
Version: 1.1.2
Release: 1
Summary: Mustache template engine for Django 1.8 and newer, with support for Django context processors.
License: MIT
URL: https://github.com/wq/django-mustache
Source0: https://mirrors.nju.edu.cn/pypi/web/packages/08/69/07a0c00262321044945b7edbe5482e687399a3fe3ed74797dde4b5115600/django-mustache-1.1.2.tar.gz
BuildArch: noarch
Requires: python3-Django
Requires: python3-pystache
%description
# django-mustache
A straightforward Mustache-powered template engine for Django, extracted from [wq.db] and updated to support the new [template backend] infrastructure in Django 1.8 and newer. *django-mustache* facilitates [progressive enhancement] by allowing you to share the same templates between Django and an offline-capable JavaScript [web app]. Combined with a shared [URL structure], this approach ensures that each page in your site can be selectively rendered on the [server or on the client][templates] as needed.
A number of Pystache/Mustache backends for Django exist, though many are outdated. Only this library provides all of the following:
* Full integration with existing Django context processors like `django.template.context_processors.csrf` and `django.contrib.auth.context_processors.auth`.*
* Full test suite
* Installable via PyPI
* Compatible with Django 1.8 and newer
> *[wq/app.js] provides client-side equivalents for these context variables.
[](https://pypi.org/project/django-mustache)
[](https://github.com/wq/django-mustache/releases)
[](https://github.com/wq/django-mustache/blob/master/LICENSE)
[](https://github.com/wq/django-mustache/stargazers)
[](https://github.com/wq/django-mustache/network)
[](https://github.com/wq/django-mustache/issues)
[](https://travis-ci.org/wq/django-mustache)
[](https://pypi.org/project/django-mustache)
[](https://pypi.org/project/django-mustache)
### Usage
```bash
pip3 install django-mustache
```
Configure django-mustache like you would any [template backend]:
```python
# myproject/settings.py
TEMPLATES = [
{
'BACKEND': 'django_mustache.Mustache',
'DIRS': [ '...' ],
'APP_DIRS': False,
'OPTIONS': {
'context_processors': [ '...' ],
'partials_dir': 'partials',
'file_extension': 'html',
}
},
# ...
]
```
The following configuration options are supported:
* **context_processors**: equivalent to the Django template backend setting. The goal is to be able to use the same context processors for both Django and Mustache template backends. (Let us know if you come across any compatibility issues.)
* **partials_dir**: If set, django-mustache will check each template directory for a subfolder containing Mustache partial templates. The default partial folder name is 'partials'. Set to `False` to disable this feature.
* **file_extension**: File extension to use when searching for templates and partials. The default is '.html', which should not conflict with existing Django templates as long as completely separate directories are configured for Mustache templates. Django views typically include the extension in the template name - this is taken into account when searching for templates.
[wq.db]: https://wq.io/wq.db/
[template backend]: https://docs.djangoproject.com/en/1.10/topics/templates
[progressive enhancement]: https://wq.io/docs/website
[web app]: https://wq.io/docs/web-app
[URL structure]: https://wq.io/docs/url-structure
[templates]: https://wq.io/docs/templates
[wq/app.js]: https://wq.io/docs/app-js
%package -n python3-django-mustache
Summary: Mustache template engine for Django 1.8 and newer, with support for Django context processors.
Provides: python-django-mustache
BuildRequires: python3-devel
BuildRequires: python3-setuptools
BuildRequires: python3-pip
%description -n python3-django-mustache
# django-mustache
A straightforward Mustache-powered template engine for Django, extracted from [wq.db] and updated to support the new [template backend] infrastructure in Django 1.8 and newer. *django-mustache* facilitates [progressive enhancement] by allowing you to share the same templates between Django and an offline-capable JavaScript [web app]. Combined with a shared [URL structure], this approach ensures that each page in your site can be selectively rendered on the [server or on the client][templates] as needed.
A number of Pystache/Mustache backends for Django exist, though many are outdated. Only this library provides all of the following:
* Full integration with existing Django context processors like `django.template.context_processors.csrf` and `django.contrib.auth.context_processors.auth`.*
* Full test suite
* Installable via PyPI
* Compatible with Django 1.8 and newer
> *[wq/app.js] provides client-side equivalents for these context variables.
[](https://pypi.org/project/django-mustache)
[](https://github.com/wq/django-mustache/releases)
[](https://github.com/wq/django-mustache/blob/master/LICENSE)
[](https://github.com/wq/django-mustache/stargazers)
[](https://github.com/wq/django-mustache/network)
[](https://github.com/wq/django-mustache/issues)
[](https://travis-ci.org/wq/django-mustache)
[](https://pypi.org/project/django-mustache)
[](https://pypi.org/project/django-mustache)
### Usage
```bash
pip3 install django-mustache
```
Configure django-mustache like you would any [template backend]:
```python
# myproject/settings.py
TEMPLATES = [
{
'BACKEND': 'django_mustache.Mustache',
'DIRS': [ '...' ],
'APP_DIRS': False,
'OPTIONS': {
'context_processors': [ '...' ],
'partials_dir': 'partials',
'file_extension': 'html',
}
},
# ...
]
```
The following configuration options are supported:
* **context_processors**: equivalent to the Django template backend setting. The goal is to be able to use the same context processors for both Django and Mustache template backends. (Let us know if you come across any compatibility issues.)
* **partials_dir**: If set, django-mustache will check each template directory for a subfolder containing Mustache partial templates. The default partial folder name is 'partials'. Set to `False` to disable this feature.
* **file_extension**: File extension to use when searching for templates and partials. The default is '.html', which should not conflict with existing Django templates as long as completely separate directories are configured for Mustache templates. Django views typically include the extension in the template name - this is taken into account when searching for templates.
[wq.db]: https://wq.io/wq.db/
[template backend]: https://docs.djangoproject.com/en/1.10/topics/templates
[progressive enhancement]: https://wq.io/docs/website
[web app]: https://wq.io/docs/web-app
[URL structure]: https://wq.io/docs/url-structure
[templates]: https://wq.io/docs/templates
[wq/app.js]: https://wq.io/docs/app-js
%package help
Summary: Development documents and examples for django-mustache
Provides: python3-django-mustache-doc
%description help
# django-mustache
A straightforward Mustache-powered template engine for Django, extracted from [wq.db] and updated to support the new [template backend] infrastructure in Django 1.8 and newer. *django-mustache* facilitates [progressive enhancement] by allowing you to share the same templates between Django and an offline-capable JavaScript [web app]. Combined with a shared [URL structure], this approach ensures that each page in your site can be selectively rendered on the [server or on the client][templates] as needed.
A number of Pystache/Mustache backends for Django exist, though many are outdated. Only this library provides all of the following:
* Full integration with existing Django context processors like `django.template.context_processors.csrf` and `django.contrib.auth.context_processors.auth`.*
* Full test suite
* Installable via PyPI
* Compatible with Django 1.8 and newer
> *[wq/app.js] provides client-side equivalents for these context variables.
[](https://pypi.org/project/django-mustache)
[](https://github.com/wq/django-mustache/releases)
[](https://github.com/wq/django-mustache/blob/master/LICENSE)
[](https://github.com/wq/django-mustache/stargazers)
[](https://github.com/wq/django-mustache/network)
[](https://github.com/wq/django-mustache/issues)
[](https://travis-ci.org/wq/django-mustache)
[](https://pypi.org/project/django-mustache)
[](https://pypi.org/project/django-mustache)
### Usage
```bash
pip3 install django-mustache
```
Configure django-mustache like you would any [template backend]:
```python
# myproject/settings.py
TEMPLATES = [
{
'BACKEND': 'django_mustache.Mustache',
'DIRS': [ '...' ],
'APP_DIRS': False,
'OPTIONS': {
'context_processors': [ '...' ],
'partials_dir': 'partials',
'file_extension': 'html',
}
},
# ...
]
```
The following configuration options are supported:
* **context_processors**: equivalent to the Django template backend setting. The goal is to be able to use the same context processors for both Django and Mustache template backends. (Let us know if you come across any compatibility issues.)
* **partials_dir**: If set, django-mustache will check each template directory for a subfolder containing Mustache partial templates. The default partial folder name is 'partials'. Set to `False` to disable this feature.
* **file_extension**: File extension to use when searching for templates and partials. The default is '.html', which should not conflict with existing Django templates as long as completely separate directories are configured for Mustache templates. Django views typically include the extension in the template name - this is taken into account when searching for templates.
[wq.db]: https://wq.io/wq.db/
[template backend]: https://docs.djangoproject.com/en/1.10/topics/templates
[progressive enhancement]: https://wq.io/docs/website
[web app]: https://wq.io/docs/web-app
[URL structure]: https://wq.io/docs/url-structure
[templates]: https://wq.io/docs/templates
[wq/app.js]: https://wq.io/docs/app-js
%prep
%autosetup -n django-mustache-1.1.2
%build
%py3_build
%install
%py3_install
install -d -m755 %{buildroot}/%{_pkgdocdir}
if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi
if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi
if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi
if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi
pushd %{buildroot}
if [ -d usr/lib ]; then
find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/lib64 ]; then
find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/bin ]; then
find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/sbin ]; then
find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst
fi
touch doclist.lst
if [ -d usr/share/man ]; then
find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst
fi
popd
mv %{buildroot}/filelist.lst .
mv %{buildroot}/doclist.lst .
%files -n python3-django-mustache -f filelist.lst
%dir %{python3_sitelib}/*
%files help -f doclist.lst
%{_docdir}/*
%changelog
* Tue May 30 2023 Python_Bot <Python_Bot@openeuler.org> - 1.1.2-1
- Package Spec generated
|
