django-components 0.64__tar.gz → 0.65__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- {django_components-0.64/src/django_components.egg-info → django_components-0.65}/PKG-INFO +21 -9
- {django_components-0.64 → django_components-0.65}/README.md +20 -8
- {django_components-0.64 → django_components-0.65}/pyproject.toml +1 -1
- {django_components-0.64 → django_components-0.65}/src/django_components/component.py +19 -13
- {django_components-0.64 → django_components-0.65/src/django_components.egg-info}/PKG-INFO +21 -9
- {django_components-0.64 → django_components-0.65}/tests/test_component.py +18 -0
- {django_components-0.64 → django_components-0.65}/LICENSE +0 -0
- {django_components-0.64 → django_components-0.65}/setup.cfg +0 -0
- {django_components-0.64 → django_components-0.65}/src/django_components/__init__.py +0 -0
- {django_components-0.64 → django_components-0.65}/src/django_components/app_settings.py +0 -0
- {django_components-0.64 → django_components-0.65}/src/django_components/apps.py +0 -0
- {django_components-0.64 → django_components-0.65}/src/django_components/component_registry.py +0 -0
- {django_components-0.64 → django_components-0.65}/src/django_components/logger.py +0 -0
- {django_components-0.64 → django_components-0.65}/src/django_components/management/__init__.py +0 -0
- {django_components-0.64 → django_components-0.65}/src/django_components/management/commands/__init__.py +0 -0
- {django_components-0.64 → django_components-0.65}/src/django_components/management/commands/startcomponent.py +0 -0
- {django_components-0.64 → django_components-0.65}/src/django_components/management/commands/upgradecomponent.py +0 -0
- {django_components-0.64 → django_components-0.65}/src/django_components/middleware.py +0 -0
- {django_components-0.64 → django_components-0.65}/src/django_components/py.typed +0 -0
- {django_components-0.64 → django_components-0.65}/src/django_components/safer_staticfiles/__init__.py +0 -0
- {django_components-0.64 → django_components-0.65}/src/django_components/safer_staticfiles/apps.py +0 -0
- {django_components-0.64 → django_components-0.65}/src/django_components/slots.py +0 -0
- {django_components-0.64 → django_components-0.65}/src/django_components/template_loader.py +0 -0
- {django_components-0.64 → django_components-0.65}/src/django_components/templatetags/__init__.py +0 -0
- {django_components-0.64 → django_components-0.65}/src/django_components/templatetags/component_tags.py +0 -0
- {django_components-0.64 → django_components-0.65}/src/django_components/types.py +0 -0
- {django_components-0.64 → django_components-0.65}/src/django_components/utils.py +0 -0
- {django_components-0.64 → django_components-0.65}/src/django_components.egg-info/SOURCES.txt +0 -0
- {django_components-0.64 → django_components-0.65}/src/django_components.egg-info/dependency_links.txt +0 -0
- {django_components-0.64 → django_components-0.65}/src/django_components.egg-info/requires.txt +0 -0
- {django_components-0.64 → django_components-0.65}/src/django_components.egg-info/top_level.txt +0 -0
- {django_components-0.64 → django_components-0.65}/tests/test_autodiscover.py +0 -0
- {django_components-0.64 → django_components-0.65}/tests/test_component_as_view.py +0 -0
- {django_components-0.64 → django_components-0.65}/tests/test_context.py +0 -0
- {django_components-0.64 → django_components-0.65}/tests/test_dependency_rendering.py +0 -0
- {django_components-0.64 → django_components-0.65}/tests/test_registry.py +0 -0
- {django_components-0.64 → django_components-0.65}/tests/test_settings.py +0 -0
- {django_components-0.64 → django_components-0.65}/tests/test_startcomponent_command.py +0 -0
- {django_components-0.64 → django_components-0.65}/tests/test_templatetags.py +0 -0
- {django_components-0.64 → django_components-0.65}/tests/testutils.py +0 -0
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.1
|
|
2
2
|
Name: django_components
|
|
3
|
-
Version: 0.
|
|
3
|
+
Version: 0.65
|
|
4
4
|
Summary: A way to create simple reusable template components in Django.
|
|
5
5
|
Author-email: Emil Stenström <emil@emilstenstrom.se>
|
|
6
6
|
License: MIT
|
|
@@ -179,7 +179,19 @@ Django-components supports all supported combinations versions of [Django](https
|
|
|
179
179
|
|
|
180
180
|
A component in django-components is the combination of four things: CSS, Javascript, a Django template, and some Python code to put them all together.
|
|
181
181
|
|
|
182
|
-
|
|
182
|
+
```
|
|
183
|
+
sampleproject/
|
|
184
|
+
├── calendarapp/
|
|
185
|
+
├── components/ 🆕
|
|
186
|
+
│ └── calendar/ 🆕
|
|
187
|
+
│ ├── calendar.py 🆕
|
|
188
|
+
│ ├── script.js 🆕
|
|
189
|
+
│ ├── style.css 🆕
|
|
190
|
+
│ └── template.html 🆕
|
|
191
|
+
├── sampleproject/
|
|
192
|
+
├── manage.py
|
|
193
|
+
└── requirements.txt
|
|
194
|
+
```
|
|
183
195
|
|
|
184
196
|
Start by creating empty files in the structure above.
|
|
185
197
|
|
|
@@ -205,7 +217,7 @@ Then you need a javascript file that specifies how you interact with this compon
|
|
|
205
217
|
Now you need a Django template for your component. Feel free to define more variables like `date` in this example. When creating an instance of this component we will send in the values for these variables. The template will be rendered with whatever template backend you've specified in your Django settings file.
|
|
206
218
|
|
|
207
219
|
```htmldjango
|
|
208
|
-
{# In a file called [project root]/components/calendar/
|
|
220
|
+
{# In a file called [project root]/components/calendar/template.html #}
|
|
209
221
|
<div class="calendar-component">Today's date is <span>{{ date }}</span></div>
|
|
210
222
|
```
|
|
211
223
|
|
|
@@ -221,7 +233,7 @@ from django_components import component
|
|
|
221
233
|
class Calendar(component.Component):
|
|
222
234
|
# Templates inside `[your apps]/components` dir and `[project root]/components` dir will be automatically found. To customize which template to use based on context
|
|
223
235
|
# you can override def get_template_name() instead of specifying the below variable.
|
|
224
|
-
template_name = "calendar.html"
|
|
236
|
+
template_name = "calendar/template.html"
|
|
225
237
|
|
|
226
238
|
# This component takes one parameter, a date string to show in the template
|
|
227
239
|
def get_context_data(self, date):
|
|
@@ -230,8 +242,8 @@ class Calendar(component.Component):
|
|
|
230
242
|
}
|
|
231
243
|
|
|
232
244
|
class Media:
|
|
233
|
-
css = "style.css"
|
|
234
|
-
js = "script.js"
|
|
245
|
+
css = "calendar/style.css"
|
|
246
|
+
js = "calendar/script.js"
|
|
235
247
|
```
|
|
236
248
|
|
|
237
249
|
And voilá!! We've created our first component.
|
|
@@ -262,11 +274,11 @@ The output from the above template will be:
|
|
|
262
274
|
<html>
|
|
263
275
|
<head>
|
|
264
276
|
<title>My example calendar</title>
|
|
265
|
-
<link href="style.css" type="text/css" media="all" rel="stylesheet">
|
|
277
|
+
<link href="/static/calendar/style.css" type="text/css" media="all" rel="stylesheet">
|
|
266
278
|
</head>
|
|
267
279
|
<body>
|
|
268
280
|
<div class="calendar-component">Today's date is <span>2015-06-19</span></div>
|
|
269
|
-
<script src="script.js"></script>
|
|
281
|
+
<script src="/static/calendar/script.js"></script>
|
|
270
282
|
</body>
|
|
271
283
|
<html>
|
|
272
284
|
```
|
|
@@ -331,7 +343,7 @@ In the example below we introduce two block tags that work hand in hand to make
|
|
|
331
343
|
- `{% slot <name> %}`/`{% endslot %}`: Declares a new slot in the component template.
|
|
332
344
|
- `{% fill <name> %}`/`{% endfill %}`: (Used inside a `component` tag pair.) Fills a declared slot with the specified content.
|
|
333
345
|
|
|
334
|
-
Let's update our calendar component to support more customization. We'll add `slot` tag pairs to its template,
|
|
346
|
+
Let's update our calendar component to support more customization. We'll add `slot` tag pairs to its template, _template.html_.
|
|
335
347
|
|
|
336
348
|
```htmldjango
|
|
337
349
|
<div class="calendar-component">
|
|
@@ -152,7 +152,19 @@ Django-components supports all supported combinations versions of [Django](https
|
|
|
152
152
|
|
|
153
153
|
A component in django-components is the combination of four things: CSS, Javascript, a Django template, and some Python code to put them all together.
|
|
154
154
|
|
|
155
|
-
|
|
155
|
+
```
|
|
156
|
+
sampleproject/
|
|
157
|
+
├── calendarapp/
|
|
158
|
+
├── components/ 🆕
|
|
159
|
+
│ └── calendar/ 🆕
|
|
160
|
+
│ ├── calendar.py 🆕
|
|
161
|
+
│ ├── script.js 🆕
|
|
162
|
+
│ ├── style.css 🆕
|
|
163
|
+
│ └── template.html 🆕
|
|
164
|
+
├── sampleproject/
|
|
165
|
+
├── manage.py
|
|
166
|
+
└── requirements.txt
|
|
167
|
+
```
|
|
156
168
|
|
|
157
169
|
Start by creating empty files in the structure above.
|
|
158
170
|
|
|
@@ -178,7 +190,7 @@ Then you need a javascript file that specifies how you interact with this compon
|
|
|
178
190
|
Now you need a Django template for your component. Feel free to define more variables like `date` in this example. When creating an instance of this component we will send in the values for these variables. The template will be rendered with whatever template backend you've specified in your Django settings file.
|
|
179
191
|
|
|
180
192
|
```htmldjango
|
|
181
|
-
{# In a file called [project root]/components/calendar/
|
|
193
|
+
{# In a file called [project root]/components/calendar/template.html #}
|
|
182
194
|
<div class="calendar-component">Today's date is <span>{{ date }}</span></div>
|
|
183
195
|
```
|
|
184
196
|
|
|
@@ -194,7 +206,7 @@ from django_components import component
|
|
|
194
206
|
class Calendar(component.Component):
|
|
195
207
|
# Templates inside `[your apps]/components` dir and `[project root]/components` dir will be automatically found. To customize which template to use based on context
|
|
196
208
|
# you can override def get_template_name() instead of specifying the below variable.
|
|
197
|
-
template_name = "calendar.html"
|
|
209
|
+
template_name = "calendar/template.html"
|
|
198
210
|
|
|
199
211
|
# This component takes one parameter, a date string to show in the template
|
|
200
212
|
def get_context_data(self, date):
|
|
@@ -203,8 +215,8 @@ class Calendar(component.Component):
|
|
|
203
215
|
}
|
|
204
216
|
|
|
205
217
|
class Media:
|
|
206
|
-
css = "style.css"
|
|
207
|
-
js = "script.js"
|
|
218
|
+
css = "calendar/style.css"
|
|
219
|
+
js = "calendar/script.js"
|
|
208
220
|
```
|
|
209
221
|
|
|
210
222
|
And voilá!! We've created our first component.
|
|
@@ -235,11 +247,11 @@ The output from the above template will be:
|
|
|
235
247
|
<html>
|
|
236
248
|
<head>
|
|
237
249
|
<title>My example calendar</title>
|
|
238
|
-
<link href="style.css" type="text/css" media="all" rel="stylesheet">
|
|
250
|
+
<link href="/static/calendar/style.css" type="text/css" media="all" rel="stylesheet">
|
|
239
251
|
</head>
|
|
240
252
|
<body>
|
|
241
253
|
<div class="calendar-component">Today's date is <span>2015-06-19</span></div>
|
|
242
|
-
<script src="script.js"></script>
|
|
254
|
+
<script src="/static/calendar/script.js"></script>
|
|
243
255
|
</body>
|
|
244
256
|
<html>
|
|
245
257
|
```
|
|
@@ -304,7 +316,7 @@ In the example below we introduce two block tags that work hand in hand to make
|
|
|
304
316
|
- `{% slot <name> %}`/`{% endslot %}`: Declares a new slot in the component template.
|
|
305
317
|
- `{% fill <name> %}`/`{% endfill %}`: (Used inside a `component` tag pair.) Fills a declared slot with the specified content.
|
|
306
318
|
|
|
307
|
-
Let's update our calendar component to support more customization. We'll add `slot` tag pairs to its template,
|
|
319
|
+
Let's update our calendar component to support more customization. We'll add `slot` tag pairs to its template, _template.html_.
|
|
308
320
|
|
|
309
321
|
```htmldjango
|
|
310
322
|
<div class="calendar-component">
|
|
@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
|
|
|
4
4
|
|
|
5
5
|
[project]
|
|
6
6
|
name = "django_components"
|
|
7
|
-
version = "0.
|
|
7
|
+
version = "0.65"
|
|
8
8
|
requires-python = ">=3.8, <4.0"
|
|
9
9
|
description = "A way to create simple reusable template components in Django."
|
|
10
10
|
keywords = ["django", "components", "css", "js", "html"]
|
|
@@ -1,5 +1,6 @@
|
|
|
1
1
|
import inspect
|
|
2
2
|
import os
|
|
3
|
+
import sys
|
|
3
4
|
from pathlib import Path
|
|
4
5
|
from typing import Any, ClassVar, Dict, Iterable, List, Mapping, MutableMapping, Optional, Tuple, Type, Union
|
|
5
6
|
|
|
@@ -73,7 +74,18 @@ def _resolve_component_relative_files(attrs: MutableMapping) -> None:
|
|
|
73
74
|
as the component class. If so, modify the attributes so the class Django's rendering
|
|
74
75
|
will pick up these files correctly.
|
|
75
76
|
"""
|
|
77
|
+
component_name = attrs["__qualname__"]
|
|
78
|
+
# Derive the full path of the file where the component was defined
|
|
76
79
|
module_name = attrs["__module__"]
|
|
80
|
+
module_obj = sys.modules[module_name]
|
|
81
|
+
file_path = module_obj.__file__
|
|
82
|
+
|
|
83
|
+
if not file_path:
|
|
84
|
+
logger.debug(
|
|
85
|
+
f"Could not resolve the path to the file for component '{component_name}'."
|
|
86
|
+
" Paths for HTML, JS or CSS templates will NOT be resolved relative to the component file."
|
|
87
|
+
)
|
|
88
|
+
return
|
|
77
89
|
|
|
78
90
|
# Prepare all possible directories we need to check when searching for
|
|
79
91
|
# component's template and media files
|
|
@@ -81,11 +93,11 @@ def _resolve_component_relative_files(attrs: MutableMapping) -> None:
|
|
|
81
93
|
|
|
82
94
|
# Get the directory where the component class is defined
|
|
83
95
|
try:
|
|
84
|
-
comp_dir_abs, comp_dir_rel =
|
|
96
|
+
comp_dir_abs, comp_dir_rel = _get_dir_path_from_component_path(file_path, components_dirs)
|
|
85
97
|
except RuntimeError:
|
|
86
98
|
# If no dir was found, we assume that the path is NOT relative to the component dir
|
|
87
99
|
logger.debug(
|
|
88
|
-
f"No component directory found for component '{
|
|
100
|
+
f"No component directory found for component '{component_name}' in {file_path}"
|
|
89
101
|
" If this component defines HTML, JS or CSS templates relatively to the component file,"
|
|
90
102
|
" then check that the component's directory is accessible from one of the paths"
|
|
91
103
|
" specified in the Django's 'STATICFILES_DIRS' settings."
|
|
@@ -127,17 +139,11 @@ def _resolve_component_relative_files(attrs: MutableMapping) -> None:
|
|
|
127
139
|
media.js = [resolve_file(filepath) for filepath in media.js]
|
|
128
140
|
|
|
129
141
|
|
|
130
|
-
def
|
|
131
|
-
|
|
142
|
+
def _get_dir_path_from_component_path(
|
|
143
|
+
abs_component_file_path: str,
|
|
144
|
+
candidate_dirs: Union[List[str], List[Path]],
|
|
132
145
|
) -> Tuple[str, str]:
|
|
133
|
-
|
|
134
|
-
# Thus, we should get file path relative to Django project root
|
|
135
|
-
comp_path = os.sep.join(component_module_path.split("."))
|
|
136
|
-
comp_dir_path = os.path.dirname(comp_path)
|
|
137
|
-
|
|
138
|
-
# NOTE: We assume that Django project root == current working directory!
|
|
139
|
-
cwd = os.getcwd()
|
|
140
|
-
comp_dir_path_abs = os.path.join(cwd, comp_dir_path)
|
|
146
|
+
comp_dir_path_abs = os.path.dirname(abs_component_file_path)
|
|
141
147
|
|
|
142
148
|
# From all dirs defined in settings.STATICFILES_DIRS, find one that's the parent
|
|
143
149
|
# to the component file.
|
|
@@ -150,7 +156,7 @@ def _get_dir_path_from_component_module_path(
|
|
|
150
156
|
|
|
151
157
|
if root_dir_abs is None:
|
|
152
158
|
raise RuntimeError(
|
|
153
|
-
f"Failed to resolve template directory for component '{
|
|
159
|
+
f"Failed to resolve template directory for component file '{abs_component_file_path}'",
|
|
154
160
|
)
|
|
155
161
|
|
|
156
162
|
# Derive the path from matched STATICFILES_DIRS to the dir where the current component file is.
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.1
|
|
2
2
|
Name: django_components
|
|
3
|
-
Version: 0.
|
|
3
|
+
Version: 0.65
|
|
4
4
|
Summary: A way to create simple reusable template components in Django.
|
|
5
5
|
Author-email: Emil Stenström <emil@emilstenstrom.se>
|
|
6
6
|
License: MIT
|
|
@@ -179,7 +179,19 @@ Django-components supports all supported combinations versions of [Django](https
|
|
|
179
179
|
|
|
180
180
|
A component in django-components is the combination of four things: CSS, Javascript, a Django template, and some Python code to put them all together.
|
|
181
181
|
|
|
182
|
-
|
|
182
|
+
```
|
|
183
|
+
sampleproject/
|
|
184
|
+
├── calendarapp/
|
|
185
|
+
├── components/ 🆕
|
|
186
|
+
│ └── calendar/ 🆕
|
|
187
|
+
│ ├── calendar.py 🆕
|
|
188
|
+
│ ├── script.js 🆕
|
|
189
|
+
│ ├── style.css 🆕
|
|
190
|
+
│ └── template.html 🆕
|
|
191
|
+
├── sampleproject/
|
|
192
|
+
├── manage.py
|
|
193
|
+
└── requirements.txt
|
|
194
|
+
```
|
|
183
195
|
|
|
184
196
|
Start by creating empty files in the structure above.
|
|
185
197
|
|
|
@@ -205,7 +217,7 @@ Then you need a javascript file that specifies how you interact with this compon
|
|
|
205
217
|
Now you need a Django template for your component. Feel free to define more variables like `date` in this example. When creating an instance of this component we will send in the values for these variables. The template will be rendered with whatever template backend you've specified in your Django settings file.
|
|
206
218
|
|
|
207
219
|
```htmldjango
|
|
208
|
-
{# In a file called [project root]/components/calendar/
|
|
220
|
+
{# In a file called [project root]/components/calendar/template.html #}
|
|
209
221
|
<div class="calendar-component">Today's date is <span>{{ date }}</span></div>
|
|
210
222
|
```
|
|
211
223
|
|
|
@@ -221,7 +233,7 @@ from django_components import component
|
|
|
221
233
|
class Calendar(component.Component):
|
|
222
234
|
# Templates inside `[your apps]/components` dir and `[project root]/components` dir will be automatically found. To customize which template to use based on context
|
|
223
235
|
# you can override def get_template_name() instead of specifying the below variable.
|
|
224
|
-
template_name = "calendar.html"
|
|
236
|
+
template_name = "calendar/template.html"
|
|
225
237
|
|
|
226
238
|
# This component takes one parameter, a date string to show in the template
|
|
227
239
|
def get_context_data(self, date):
|
|
@@ -230,8 +242,8 @@ class Calendar(component.Component):
|
|
|
230
242
|
}
|
|
231
243
|
|
|
232
244
|
class Media:
|
|
233
|
-
css = "style.css"
|
|
234
|
-
js = "script.js"
|
|
245
|
+
css = "calendar/style.css"
|
|
246
|
+
js = "calendar/script.js"
|
|
235
247
|
```
|
|
236
248
|
|
|
237
249
|
And voilá!! We've created our first component.
|
|
@@ -262,11 +274,11 @@ The output from the above template will be:
|
|
|
262
274
|
<html>
|
|
263
275
|
<head>
|
|
264
276
|
<title>My example calendar</title>
|
|
265
|
-
<link href="style.css" type="text/css" media="all" rel="stylesheet">
|
|
277
|
+
<link href="/static/calendar/style.css" type="text/css" media="all" rel="stylesheet">
|
|
266
278
|
</head>
|
|
267
279
|
<body>
|
|
268
280
|
<div class="calendar-component">Today's date is <span>2015-06-19</span></div>
|
|
269
|
-
<script src="script.js"></script>
|
|
281
|
+
<script src="/static/calendar/script.js"></script>
|
|
270
282
|
</body>
|
|
271
283
|
<html>
|
|
272
284
|
```
|
|
@@ -331,7 +343,7 @@ In the example below we introduce two block tags that work hand in hand to make
|
|
|
331
343
|
- `{% slot <name> %}`/`{% endslot %}`: Declares a new slot in the component template.
|
|
332
344
|
- `{% fill <name> %}`/`{% endfill %}`: (Used inside a `component` tag pair.) Fills a declared slot with the specified content.
|
|
333
345
|
|
|
334
|
-
Let's update our calendar component to support more customization. We'll add `slot` tag pairs to its template,
|
|
346
|
+
Let's update our calendar component to support more customization. We'll add `slot` tag pairs to its template, _template.html_.
|
|
335
347
|
|
|
336
348
|
```htmldjango
|
|
337
349
|
<div class="calendar-component">
|
|
@@ -186,6 +186,24 @@ class ComponentTest(SimpleTestCase):
|
|
|
186
186
|
),
|
|
187
187
|
)
|
|
188
188
|
|
|
189
|
+
def test_component_with_relative_paths_as_subcomponent(
|
|
190
|
+
self,
|
|
191
|
+
):
|
|
192
|
+
template = Template(
|
|
193
|
+
"""
|
|
194
|
+
{% load component_tags %}{% component_dependencies %}
|
|
195
|
+
{% component 'parent_component' %}
|
|
196
|
+
{% fill 'content' %}
|
|
197
|
+
{% component name='relative_file_component' variable='hello' %}
|
|
198
|
+
{% endcomponent %}
|
|
199
|
+
{% endfill %}
|
|
200
|
+
{% endcomponent %}
|
|
201
|
+
""" # NOQA
|
|
202
|
+
)
|
|
203
|
+
rendered = template.render(Context({}))
|
|
204
|
+
|
|
205
|
+
self.assertIn('<input type="text" name="variable" value="hello">', rendered, rendered)
|
|
206
|
+
|
|
189
207
|
|
|
190
208
|
class InlineComponentTest(SimpleTestCase):
|
|
191
209
|
def test_inline_html_component(self):
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
{django_components-0.64 → django_components-0.65}/src/django_components/component_registry.py
RENAMED
|
File without changes
|
|
File without changes
|
{django_components-0.64 → django_components-0.65}/src/django_components/management/__init__.py
RENAMED
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
{django_components-0.64 → django_components-0.65}/src/django_components/safer_staticfiles/apps.py
RENAMED
|
File without changes
|
|
File without changes
|
|
File without changes
|
{django_components-0.64 → django_components-0.65}/src/django_components/templatetags/__init__.py
RENAMED
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
{django_components-0.64 → django_components-0.65}/src/django_components.egg-info/SOURCES.txt
RENAMED
|
File without changes
|
|
File without changes
|
{django_components-0.64 → django_components-0.65}/src/django_components.egg-info/requires.txt
RENAMED
|
File without changes
|
{django_components-0.64 → django_components-0.65}/src/django_components.egg-info/top_level.txt
RENAMED
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|