| Awards/__init__.py |
0 |
0 |
0 |
100% |
| Awards/admin.py |
1 |
0 |
0 |
100% |
| Awards/forms.py |
17 |
1 |
0 |
94% |
| Awards/migrations/0001_initial.py |
10 |
0 |
0 |
100% |
| Awards/migrations/__init__.py |
0 |
0 |
0 |
100% |
| Awards/models.py |
51 |
11 |
0 |
78% |
| Awards/tests.py |
49 |
27 |
0 |
45% |
| Awards/urls.py |
7 |
1 |
0 |
86% |
| Awards/views.py |
62 |
48 |
0 |
23% |
| manage.py |
13 |
6 |
0 |
54% |
| project/__init__.py |
0 |
0 |
0 |
100% |
| project/settings.py |
22 |
0 |
0 |
100% |
| project/urls.py |
4 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/PIL/BlpImagePlugin.py |
262 |
227 |
0 |
13% |
| test/lib/python3.6/site-packages/PIL/BmpImagePlugin.py |
139 |
110 |
0 |
21% |
| test/lib/python3.6/site-packages/PIL/BufrStubImagePlugin.py |
28 |
15 |
0 |
46% |
| test/lib/python3.6/site-packages/PIL/CurImagePlugin.py |
30 |
19 |
0 |
37% |
| test/lib/python3.6/site-packages/PIL/DcxImagePlugin.py |
46 |
28 |
0 |
39% |
| test/lib/python3.6/site-packages/PIL/DdsImagePlugin.py |
116 |
50 |
0 |
57% |
| test/lib/python3.6/site-packages/PIL/EpsImagePlugin.py |
230 |
199 |
0 |
13% |
| test/lib/python3.6/site-packages/PIL/FitsStubImagePlugin.py |
28 |
15 |
0 |
46% |
| test/lib/python3.6/site-packages/PIL/FliImagePlugin.py |
94 |
76 |
0 |
19% |
| test/lib/python3.6/site-packages/PIL/FpxImagePlugin.py |
89 |
87 |
0 |
2% |
| test/lib/python3.6/site-packages/PIL/FtexImagePlugin.py |
34 |
20 |
0 |
41% |
| test/lib/python3.6/site-packages/PIL/GbrImagePlugin.py |
41 |
31 |
0 |
24% |
| test/lib/python3.6/site-packages/PIL/GifImagePlugin.py |
447 |
403 |
0 |
10% |
| test/lib/python3.6/site-packages/PIL/GimpGradientFile.py |
65 |
51 |
0 |
22% |
| test/lib/python3.6/site-packages/PIL/GimpPaletteFile.py |
23 |
17 |
0 |
26% |
| test/lib/python3.6/site-packages/PIL/GribStubImagePlugin.py |
29 |
15 |
0 |
48% |
| test/lib/python3.6/site-packages/PIL/Hdf5StubImagePlugin.py |
28 |
15 |
0 |
46% |
| test/lib/python3.6/site-packages/PIL/IcnsImagePlugin.py |
214 |
178 |
0 |
17% |
| test/lib/python3.6/site-packages/PIL/IcoImagePlugin.py |
137 |
109 |
0 |
20% |
| test/lib/python3.6/site-packages/PIL/ImImagePlugin.py |
171 |
128 |
0 |
25% |
| test/lib/python3.6/site-packages/PIL/Image.py |
1352 |
1034 |
0 |
24% |
| test/lib/python3.6/site-packages/PIL/ImageChops.py |
65 |
46 |
0 |
29% |
| test/lib/python3.6/site-packages/PIL/ImageColor.py |
51 |
46 |
0 |
10% |
| test/lib/python3.6/site-packages/PIL/ImageFile.py |
334 |
283 |
0 |
15% |
| test/lib/python3.6/site-packages/PIL/ImageMode.py |
23 |
18 |
0 |
22% |
| test/lib/python3.6/site-packages/PIL/ImagePalette.py |
117 |
86 |
0 |
26% |
| test/lib/python3.6/site-packages/PIL/ImageSequence.py |
32 |
25 |
0 |
22% |
| test/lib/python3.6/site-packages/PIL/ImtImagePlugin.py |
37 |
28 |
0 |
24% |
| test/lib/python3.6/site-packages/PIL/IptcImagePlugin.py |
126 |
106 |
0 |
16% |
| test/lib/python3.6/site-packages/PIL/Jpeg2KImagePlugin.py |
182 |
164 |
0 |
10% |
| test/lib/python3.6/site-packages/PIL/JpegImagePlugin.py |
402 |
361 |
0 |
10% |
| test/lib/python3.6/site-packages/PIL/JpegPresets.py |
1 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/PIL/McIdasImagePlugin.py |
29 |
20 |
0 |
31% |
| test/lib/python3.6/site-packages/PIL/MicImagePlugin.py |
50 |
49 |
0 |
2% |
| test/lib/python3.6/site-packages/PIL/MpegImagePlugin.py |
40 |
24 |
0 |
40% |
| test/lib/python3.6/site-packages/PIL/MpoImagePlugin.py |
66 |
44 |
0 |
33% |
| test/lib/python3.6/site-packages/PIL/MspImagePlugin.py |
77 |
59 |
0 |
23% |
| test/lib/python3.6/site-packages/PIL/PaletteFile.py |
24 |
19 |
0 |
21% |
| test/lib/python3.6/site-packages/PIL/PalmImagePlugin.py |
74 |
54 |
0 |
27% |
| test/lib/python3.6/site-packages/PIL/PcdImagePlugin.py |
26 |
16 |
0 |
38% |
| test/lib/python3.6/site-packages/PIL/PcxImagePlugin.py |
77 |
60 |
0 |
22% |
| test/lib/python3.6/site-packages/PIL/PdfImagePlugin.py |
103 |
92 |
0 |
11% |
| test/lib/python3.6/site-packages/PIL/PdfParser.py |
653 |
524 |
2 |
20% |
| test/lib/python3.6/site-packages/PIL/PixarImagePlugin.py |
20 |
10 |
0 |
50% |
| test/lib/python3.6/site-packages/PIL/PngImagePlugin.py |
502 |
425 |
0 |
15% |
| test/lib/python3.6/site-packages/PIL/PpmImagePlugin.py |
89 |
74 |
0 |
17% |
| test/lib/python3.6/site-packages/PIL/PsdImagePlugin.py |
180 |
159 |
0 |
12% |
| test/lib/python3.6/site-packages/PIL/SgiImagePlugin.py |
111 |
90 |
0 |
19% |
| test/lib/python3.6/site-packages/PIL/SpiderImagePlugin.py |
194 |
166 |
0 |
14% |
| test/lib/python3.6/site-packages/PIL/SunImagePlugin.py |
51 |
41 |
0 |
20% |
| test/lib/python3.6/site-packages/PIL/TgaImagePlugin.py |
97 |
82 |
0 |
15% |
| test/lib/python3.6/site-packages/PIL/TiffImagePlugin.py |
976 |
741 |
0 |
24% |
| test/lib/python3.6/site-packages/PIL/TiffTags.py |
40 |
2 |
0 |
95% |
| test/lib/python3.6/site-packages/PIL/WebPImagePlugin.py |
207 |
176 |
0 |
15% |
| test/lib/python3.6/site-packages/PIL/WmfImagePlugin.py |
65 |
45 |
0 |
31% |
| test/lib/python3.6/site-packages/PIL/XVThumbImagePlugin.py |
30 |
15 |
0 |
50% |
| test/lib/python3.6/site-packages/PIL/XbmImagePlugin.py |
35 |
21 |
0 |
40% |
| test/lib/python3.6/site-packages/PIL/XpmImagePlugin.py |
57 |
43 |
0 |
25% |
| test/lib/python3.6/site-packages/PIL/__init__.py |
4 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/PIL/_binary.py |
31 |
15 |
0 |
52% |
| test/lib/python3.6/site-packages/PIL/_util.py |
24 |
10 |
0 |
58% |
| test/lib/python3.6/site-packages/PIL/_version.py |
1 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/bootstrap4/__init__.py |
1 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/bootstrap4/_version.py |
1 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/bootstrap4/bootstrap.py |
38 |
22 |
0 |
42% |
| test/lib/python3.6/site-packages/bootstrap4/components.py |
15 |
10 |
0 |
33% |
| test/lib/python3.6/site-packages/bootstrap4/exceptions.py |
2 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/bootstrap4/forms.py |
87 |
70 |
0 |
20% |
| test/lib/python3.6/site-packages/bootstrap4/models.py |
0 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/bootstrap4/templatetags/__init__.py |
0 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/bootstrap4/templatetags/bootstrap4.py |
187 |
144 |
0 |
23% |
| test/lib/python3.6/site-packages/bootstrap4/text.py |
12 |
8 |
0 |
33% |
| test/lib/python3.6/site-packages/bootstrap4/utils.py |
90 |
65 |
0 |
28% |
| test/lib/python3.6/site-packages/confusable_homoglyphs/__init__.py |
6 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/confusable_homoglyphs/_version.py |
5 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/confusable_homoglyphs/categories.py |
23 |
17 |
0 |
26% |
| test/lib/python3.6/site-packages/confusable_homoglyphs/confusables.py |
43 |
35 |
0 |
19% |
| test/lib/python3.6/site-packages/confusable_homoglyphs/utils.py |
29 |
14 |
0 |
52% |
| test/lib/python3.6/site-packages/django/__init__.py |
14 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/apps/__init__.py |
3 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/apps/config.py |
86 |
22 |
0 |
74% |
| test/lib/python3.6/site-packages/django/apps/registry.py |
168 |
34 |
0 |
80% |
| test/lib/python3.6/site-packages/django/conf/__init__.py |
95 |
34 |
0 |
64% |
| test/lib/python3.6/site-packages/django/conf/global_settings.py |
144 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/conf/locale/__init__.py |
2 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/conf/urls/__init__.py |
44 |
12 |
0 |
73% |
| test/lib/python3.6/site-packages/django/conf/urls/static.py |
11 |
5 |
0 |
55% |
| test/lib/python3.6/site-packages/django/contrib/__init__.py |
0 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/contrib/admin/__init__.py |
10 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/contrib/admin/actions.py |
36 |
26 |
0 |
28% |
| test/lib/python3.6/site-packages/django/contrib/admin/apps.py |
14 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/contrib/admin/checks.py |
425 |
215 |
0 |
49% |
| test/lib/python3.6/site-packages/django/contrib/admin/decorators.py |
14 |
3 |
0 |
79% |
| test/lib/python3.6/site-packages/django/contrib/admin/exceptions.py |
5 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/contrib/admin/filters.py |
209 |
144 |
0 |
31% |
| test/lib/python3.6/site-packages/django/contrib/admin/helpers.py |
236 |
172 |
0 |
27% |
| test/lib/python3.6/site-packages/django/contrib/admin/migrations/0001_initial.py |
7 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/contrib/admin/migrations/0002_logentry_remove_auto_add.py |
6 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/contrib/admin/migrations/__init__.py |
0 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/contrib/admin/models.py |
86 |
46 |
0 |
47% |
| test/lib/python3.6/site-packages/django/contrib/admin/options.py |
957 |
737 |
0 |
23% |
| test/lib/python3.6/site-packages/django/contrib/admin/sites.py |
223 |
115 |
0 |
48% |
| test/lib/python3.6/site-packages/django/contrib/admin/templatetags/__init__.py |
0 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/contrib/admin/templatetags/admin_list.py |
222 |
186 |
0 |
16% |
| test/lib/python3.6/site-packages/django/contrib/admin/templatetags/admin_modify.py |
36 |
29 |
0 |
19% |
| test/lib/python3.6/site-packages/django/contrib/admin/templatetags/admin_static.py |
5 |
1 |
0 |
80% |
| test/lib/python3.6/site-packages/django/contrib/admin/templatetags/admin_urls.py |
38 |
28 |
0 |
26% |
| test/lib/python3.6/site-packages/django/contrib/admin/templatetags/log.py |
29 |
21 |
0 |
28% |
| test/lib/python3.6/site-packages/django/contrib/admin/utils.py |
315 |
255 |
0 |
19% |
| test/lib/python3.6/site-packages/django/contrib/admin/views/__init__.py |
0 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/contrib/admin/views/main.py |
246 |
211 |
0 |
14% |
| test/lib/python3.6/site-packages/django/contrib/admin/widgets.py |
225 |
154 |
0 |
32% |
| test/lib/python3.6/site-packages/django/contrib/auth/__init__.py |
131 |
99 |
0 |
24% |
| test/lib/python3.6/site-packages/django/contrib/auth/admin.py |
106 |
53 |
0 |
50% |
| test/lib/python3.6/site-packages/django/contrib/auth/apps.py |
13 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/contrib/auth/base_user.py |
77 |
35 |
0 |
55% |
| test/lib/python3.6/site-packages/django/contrib/auth/checks.py |
54 |
23 |
0 |
57% |
| test/lib/python3.6/site-packages/django/contrib/auth/decorators.py |
39 |
20 |
0 |
49% |
| test/lib/python3.6/site-packages/django/contrib/auth/forms.py |
194 |
113 |
0 |
42% |
| test/lib/python3.6/site-packages/django/contrib/auth/hashers.py |
314 |
205 |
0 |
35% |
| test/lib/python3.6/site-packages/django/contrib/auth/management/__init__.py |
74 |
35 |
0 |
53% |
| test/lib/python3.6/site-packages/django/contrib/auth/migrations/0001_initial.py |
8 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/contrib/auth/migrations/0002_alter_permission_name_max_length.py |
5 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/contrib/auth/migrations/0003_alter_user_email_max_length.py |
5 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/contrib/auth/migrations/0004_alter_user_username_opts.py |
7 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/contrib/auth/migrations/0005_alter_user_last_login_null.py |
5 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/contrib/auth/migrations/0006_require_contenttypes_0002.py |
5 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/contrib/auth/migrations/0007_alter_validators_add_error_messages.py |
7 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/contrib/auth/migrations/0008_alter_user_username_max_length.py |
7 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/contrib/auth/migrations/__init__.py |
0 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/contrib/auth/models.py |
208 |
90 |
0 |
57% |
| test/lib/python3.6/site-packages/django/contrib/auth/password_validation.py |
107 |
68 |
0 |
36% |
| test/lib/python3.6/site-packages/django/contrib/auth/signals.py |
4 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/contrib/auth/tokens.py |
37 |
23 |
0 |
38% |
| test/lib/python3.6/site-packages/django/contrib/auth/validators.py |
15 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/contrib/auth/views.py |
328 |
197 |
0 |
40% |
| test/lib/python3.6/site-packages/django/contrib/contenttypes/__init__.py |
1 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/contrib/contenttypes/admin.py |
55 |
32 |
0 |
42% |
| test/lib/python3.6/site-packages/django/contrib/contenttypes/apps.py |
13 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/contrib/contenttypes/checks.py |
14 |
2 |
0 |
86% |
| test/lib/python3.6/site-packages/django/contrib/contenttypes/fields.py |
344 |
278 |
0 |
19% |
| test/lib/python3.6/site-packages/django/contrib/contenttypes/forms.py |
38 |
28 |
0 |
26% |
| test/lib/python3.6/site-packages/django/contrib/contenttypes/management/__init__.py |
79 |
36 |
0 |
54% |
| test/lib/python3.6/site-packages/django/contrib/contenttypes/migrations/0001_initial.py |
6 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/contrib/contenttypes/migrations/0002_remove_content_type_name.py |
13 |
7 |
0 |
46% |
| test/lib/python3.6/site-packages/django/contrib/contenttypes/migrations/__init__.py |
0 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/contrib/contenttypes/models.py |
107 |
52 |
0 |
51% |
| test/lib/python3.6/site-packages/django/contrib/contenttypes/views.py |
55 |
47 |
0 |
15% |
| test/lib/python3.6/site-packages/django/contrib/messages/__init__.py |
3 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/contrib/messages/api.py |
34 |
20 |
0 |
41% |
| test/lib/python3.6/site-packages/django/contrib/messages/apps.py |
5 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/contrib/messages/constants.py |
7 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/contrib/messages/storage/__init__.py |
4 |
1 |
0 |
75% |
| test/lib/python3.6/site-packages/django/contrib/sessions/__init__.py |
1 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/contrib/sessions/apps.py |
5 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/contrib/sessions/base_session.py |
31 |
11 |
0 |
65% |
| test/lib/python3.6/site-packages/django/contrib/sessions/management/__init__.py |
0 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/contrib/sessions/migrations/0001_initial.py |
6 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/contrib/sessions/migrations/__init__.py |
0 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/contrib/sessions/models.py |
11 |
2 |
0 |
82% |
| test/lib/python3.6/site-packages/django/contrib/sites/__init__.py |
1 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/contrib/sites/requests.py |
12 |
4 |
0 |
67% |
| test/lib/python3.6/site-packages/django/contrib/sites/shortcuts.py |
8 |
5 |
0 |
38% |
| test/lib/python3.6/site-packages/django/contrib/staticfiles/__init__.py |
1 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/contrib/staticfiles/apps.py |
6 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/contrib/staticfiles/finders.py |
156 |
58 |
0 |
63% |
| test/lib/python3.6/site-packages/django/contrib/staticfiles/management/__init__.py |
0 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/contrib/staticfiles/templatetags/__init__.py |
0 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/contrib/staticfiles/templatetags/staticfiles.py |
7 |
2 |
0 |
71% |
| test/lib/python3.6/site-packages/django/contrib/staticfiles/utils.py |
37 |
30 |
0 |
19% |
| test/lib/python3.6/site-packages/django/core/__init__.py |
0 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/core/cache/__init__.py |
62 |
21 |
0 |
66% |
| test/lib/python3.6/site-packages/django/core/cache/backends/__init__.py |
0 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/core/cache/backends/base.py |
117 |
66 |
0 |
44% |
| test/lib/python3.6/site-packages/django/core/cache/backends/db.py |
139 |
117 |
0 |
16% |
| test/lib/python3.6/site-packages/django/core/cache/backends/locmem.py |
109 |
82 |
0 |
25% |
| test/lib/python3.6/site-packages/django/core/cache/utils.py |
11 |
5 |
0 |
55% |
| test/lib/python3.6/site-packages/django/core/checks/__init__.py |
14 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/core/checks/caches.py |
9 |
1 |
0 |
89% |
| test/lib/python3.6/site-packages/django/core/checks/compatibility/__init__.py |
0 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/core/checks/compatibility/django_1_10.py |
7 |
1 |
0 |
86% |
| test/lib/python3.6/site-packages/django/core/checks/compatibility/django_1_8_0.py |
10 |
1 |
0 |
90% |
| test/lib/python3.6/site-packages/django/core/checks/database.py |
7 |
4 |
0 |
43% |
| test/lib/python3.6/site-packages/django/core/checks/messages.py |
52 |
18 |
0 |
65% |
| test/lib/python3.6/site-packages/django/core/checks/model_checks.py |
65 |
43 |
0 |
34% |
| test/lib/python3.6/site-packages/django/core/checks/registry.py |
56 |
4 |
0 |
93% |
| test/lib/python3.6/site-packages/django/core/checks/security/__init__.py |
0 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/core/checks/security/base.py |
56 |
25 |
0 |
55% |
| test/lib/python3.6/site-packages/django/core/checks/security/csrf.py |
13 |
5 |
0 |
62% |
| test/lib/python3.6/site-packages/django/core/checks/security/sessions.py |
37 |
20 |
0 |
46% |
| test/lib/python3.6/site-packages/django/core/checks/templates.py |
24 |
5 |
0 |
79% |
| test/lib/python3.6/site-packages/django/core/checks/urls.py |
56 |
14 |
0 |
75% |
| test/lib/python3.6/site-packages/django/core/checks/utils.py |
7 |
4 |
0 |
43% |
| test/lib/python3.6/site-packages/django/core/exceptions.py |
93 |
47 |
0 |
49% |
| test/lib/python3.6/site-packages/django/core/files/__init__.py |
2 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/core/files/base.py |
116 |
79 |
0 |
32% |
| test/lib/python3.6/site-packages/django/core/files/images.py |
44 |
36 |
0 |
18% |
| test/lib/python3.6/site-packages/django/core/files/locks.py |
57 |
46 |
0 |
19% |
| test/lib/python3.6/site-packages/django/core/files/move.py |
37 |
31 |
0 |
16% |
| test/lib/python3.6/site-packages/django/core/files/storage.py |
218 |
140 |
0 |
36% |
| test/lib/python3.6/site-packages/django/core/files/temp.py |
33 |
26 |
0 |
21% |
| test/lib/python3.6/site-packages/django/core/files/uploadedfile.py |
58 |
31 |
0 |
47% |
| test/lib/python3.6/site-packages/django/core/files/uploadhandler.py |
78 |
42 |
0 |
46% |
| test/lib/python3.6/site-packages/django/core/files/utils.py |
39 |
17 |
0 |
56% |
| test/lib/python3.6/site-packages/django/core/handlers/__init__.py |
0 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/core/handlers/base.py |
150 |
119 |
0 |
21% |
| test/lib/python3.6/site-packages/django/core/handlers/exception.py |
70 |
50 |
0 |
29% |
| test/lib/python3.6/site-packages/django/core/handlers/wsgi.py |
141 |
104 |
0 |
26% |
| test/lib/python3.6/site-packages/django/core/mail/__init__.py |
33 |
22 |
0 |
33% |
| test/lib/python3.6/site-packages/django/core/mail/message.py |
275 |
210 |
0 |
24% |
| test/lib/python3.6/site-packages/django/core/mail/utils.py |
9 |
4 |
0 |
56% |
| test/lib/python3.6/site-packages/django/core/management/__init__.py |
165 |
83 |
0 |
50% |
| test/lib/python3.6/site-packages/django/core/management/base.py |
213 |
81 |
0 |
62% |
| test/lib/python3.6/site-packages/django/core/management/color.py |
30 |
5 |
0 |
83% |
| test/lib/python3.6/site-packages/django/core/management/commands/__init__.py |
0 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/core/management/commands/check.py |
30 |
8 |
0 |
73% |
| test/lib/python3.6/site-packages/django/core/management/commands/createcachetable.py |
68 |
45 |
0 |
34% |
| test/lib/python3.6/site-packages/django/core/management/commands/migrate.py |
161 |
85 |
0 |
47% |
| test/lib/python3.6/site-packages/django/core/management/commands/test.py |
33 |
3 |
0 |
91% |
| test/lib/python3.6/site-packages/django/core/management/sql.py |
24 |
8 |
0 |
67% |
| test/lib/python3.6/site-packages/django/core/paginator.py |
91 |
55 |
0 |
40% |
| test/lib/python3.6/site-packages/django/core/serializers/__init__.py |
108 |
25 |
0 |
77% |
| test/lib/python3.6/site-packages/django/core/serializers/base.py |
109 |
43 |
0 |
61% |
| test/lib/python3.6/site-packages/django/core/serializers/json.py |
85 |
42 |
0 |
51% |
| test/lib/python3.6/site-packages/django/core/serializers/python.py |
122 |
88 |
0 |
28% |
| test/lib/python3.6/site-packages/django/core/serializers/pyyaml.py |
44 |
39 |
0 |
11% |
| test/lib/python3.6/site-packages/django/core/serializers/xml_serializer.py |
220 |
172 |
0 |
22% |
| test/lib/python3.6/site-packages/django/core/servers/__init__.py |
0 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/core/servers/basehttp.py |
88 |
62 |
0 |
30% |
| test/lib/python3.6/site-packages/django/core/signals.py |
5 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/core/signing.py |
94 |
59 |
0 |
37% |
| test/lib/python3.6/site-packages/django/core/validators.py |
261 |
122 |
0 |
53% |
| test/lib/python3.6/site-packages/django/core/wsgi.py |
5 |
2 |
0 |
60% |
| test/lib/python3.6/site-packages/django/db/__init__.py |
26 |
8 |
0 |
69% |
| test/lib/python3.6/site-packages/django/db/backends/__init__.py |
0 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/db/backends/base/__init__.py |
0 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/db/backends/base/base.py |
303 |
84 |
0 |
72% |
| test/lib/python3.6/site-packages/django/db/backends/base/client.py |
6 |
1 |
0 |
83% |
| test/lib/python3.6/site-packages/django/db/backends/base/creation.py |
122 |
52 |
0 |
57% |
| test/lib/python3.6/site-packages/django/db/backends/base/features.py |
106 |
18 |
0 |
83% |
| test/lib/python3.6/site-packages/django/db/backends/base/introspection.py |
74 |
51 |
0 |
31% |
| test/lib/python3.6/site-packages/django/db/backends/base/operations.py |
205 |
107 |
0 |
48% |
| test/lib/python3.6/site-packages/django/db/backends/base/schema.py |
441 |
249 |
0 |
44% |
| test/lib/python3.6/site-packages/django/db/backends/base/validation.py |
7 |
1 |
0 |
86% |
| test/lib/python3.6/site-packages/django/db/backends/signals.py |
2 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/db/backends/sqlite3/__init__.py |
0 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/db/backends/sqlite3/base.py |
254 |
129 |
0 |
49% |
| test/lib/python3.6/site-packages/django/db/backends/sqlite3/client.py |
7 |
2 |
0 |
71% |
| test/lib/python3.6/site-packages/django/db/backends/sqlite3/creation.py |
77 |
44 |
0 |
43% |
| test/lib/python3.6/site-packages/django/db/backends/sqlite3/features.py |
46 |
11 |
0 |
76% |
| test/lib/python3.6/site-packages/django/db/backends/sqlite3/introspection.py |
132 |
109 |
0 |
17% |
| test/lib/python3.6/site-packages/django/db/backends/sqlite3/operations.py |
164 |
94 |
0 |
43% |
| test/lib/python3.6/site-packages/django/db/backends/sqlite3/schema.py |
133 |
50 |
0 |
62% |
| test/lib/python3.6/site-packages/django/db/backends/utils.py |
134 |
82 |
0 |
39% |
| test/lib/python3.6/site-packages/django/db/migrations/__init__.py |
2 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/db/migrations/autodetector.py |
602 |
548 |
0 |
9% |
| test/lib/python3.6/site-packages/django/db/migrations/exceptions.py |
29 |
5 |
0 |
83% |
| test/lib/python3.6/site-packages/django/db/migrations/executor.py |
204 |
127 |
0 |
38% |
| test/lib/python3.6/site-packages/django/db/migrations/graph.py |
241 |
117 |
0 |
51% |
| test/lib/python3.6/site-packages/django/db/migrations/loader.py |
170 |
66 |
0 |
61% |
| test/lib/python3.6/site-packages/django/db/migrations/migration.py |
87 |
43 |
0 |
51% |
| test/lib/python3.6/site-packages/django/db/migrations/operations/__init__.py |
4 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/db/migrations/operations/base.py |
38 |
14 |
0 |
63% |
| test/lib/python3.6/site-packages/django/db/migrations/operations/fields.py |
171 |
94 |
0 |
45% |
| test/lib/python3.6/site-packages/django/db/migrations/operations/models.py |
405 |
252 |
0 |
38% |
| test/lib/python3.6/site-packages/django/db/migrations/operations/special.py |
127 |
81 |
0 |
36% |
| test/lib/python3.6/site-packages/django/db/migrations/optimizer.py |
26 |
22 |
0 |
15% |
| test/lib/python3.6/site-packages/django/db/migrations/questioner.py |
129 |
97 |
0 |
25% |
| test/lib/python3.6/site-packages/django/db/migrations/recorder.py |
42 |
6 |
0 |
86% |
| test/lib/python3.6/site-packages/django/db/migrations/serializer.py |
284 |
204 |
0 |
28% |
| test/lib/python3.6/site-packages/django/db/migrations/state.py |
370 |
142 |
0 |
62% |
| test/lib/python3.6/site-packages/django/db/migrations/topological_sort.py |
15 |
13 |
0 |
13% |
| test/lib/python3.6/site-packages/django/db/migrations/utils.py |
11 |
4 |
0 |
64% |
| test/lib/python3.6/site-packages/django/db/migrations/writer.py |
183 |
147 |
0 |
20% |
| test/lib/python3.6/site-packages/django/db/models/__init__.py |
29 |
9 |
0 |
69% |
| test/lib/python3.6/site-packages/django/db/models/aggregates.py |
89 |
47 |
0 |
47% |
| test/lib/python3.6/site-packages/django/db/models/base.py |
868 |
454 |
0 |
48% |
| test/lib/python3.6/site-packages/django/db/models/constants.py |
1 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/db/models/deletion.py |
171 |
101 |
0 |
41% |
| test/lib/python3.6/site-packages/django/db/models/expressions.py |
667 |
413 |
0 |
38% |
| test/lib/python3.6/site-packages/django/db/models/fields/__init__.py |
1303 |
616 |
0 |
53% |
| test/lib/python3.6/site-packages/django/db/models/fields/files.py |
250 |
129 |
0 |
48% |
| test/lib/python3.6/site-packages/django/db/models/fields/proxy.py |
10 |
6 |
0 |
40% |
| test/lib/python3.6/site-packages/django/db/models/fields/related.py |
754 |
252 |
0 |
67% |
| test/lib/python3.6/site-packages/django/db/models/fields/related_descriptors.py |
524 |
464 |
0 |
11% |
| test/lib/python3.6/site-packages/django/db/models/fields/related_lookups.py |
87 |
44 |
0 |
49% |
| test/lib/python3.6/site-packages/django/db/models/fields/reverse_related.py |
119 |
35 |
0 |
71% |
| test/lib/python3.6/site-packages/django/db/models/functions/__init__.py |
3 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/db/models/functions/base.py |
115 |
63 |
0 |
45% |
| test/lib/python3.6/site-packages/django/db/models/functions/datetime.py |
167 |
85 |
0 |
49% |
| test/lib/python3.6/site-packages/django/db/models/indexes.py |
69 |
50 |
0 |
28% |
| test/lib/python3.6/site-packages/django/db/models/lookups.py |
401 |
160 |
0 |
60% |
| test/lib/python3.6/site-packages/django/db/models/manager.py |
106 |
10 |
0 |
91% |
| test/lib/python3.6/site-packages/django/db/models/options.py |
440 |
112 |
0 |
75% |
| test/lib/python3.6/site-packages/django/db/models/query.py |
926 |
600 |
0 |
35% |
| test/lib/python3.6/site-packages/django/db/models/query_utils.py |
140 |
65 |
0 |
54% |
| test/lib/python3.6/site-packages/django/db/models/signals.py |
30 |
5 |
0 |
83% |
| test/lib/python3.6/site-packages/django/db/models/sql/__init__.py |
5 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/db/models/sql/compiler.py |
711 |
380 |
0 |
47% |
| test/lib/python3.6/site-packages/django/db/models/sql/constants.py |
11 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/db/models/sql/datastructures.py |
64 |
17 |
0 |
73% |
| test/lib/python3.6/site-packages/django/db/models/sql/query.py |
1077 |
602 |
0 |
44% |
| test/lib/python3.6/site-packages/django/db/models/sql/subqueries.py |
106 |
63 |
0 |
41% |
| test/lib/python3.6/site-packages/django/db/models/sql/where.py |
119 |
56 |
0 |
53% |
| test/lib/python3.6/site-packages/django/db/models/utils.py |
13 |
3 |
0 |
77% |
| test/lib/python3.6/site-packages/django/db/transaction.py |
116 |
51 |
0 |
56% |
| test/lib/python3.6/site-packages/django/db/utils.py |
189 |
61 |
0 |
68% |
| test/lib/python3.6/site-packages/django/dispatch/__init__.py |
1 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/dispatch/dispatcher.py |
134 |
36 |
0 |
73% |
| test/lib/python3.6/site-packages/django/forms/__init__.py |
7 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/forms/boundfield.py |
158 |
112 |
0 |
29% |
| test/lib/python3.6/site-packages/django/forms/fields.py |
698 |
460 |
0 |
34% |
| test/lib/python3.6/site-packages/django/forms/forms.py |
252 |
180 |
0 |
29% |
| test/lib/python3.6/site-packages/django/forms/formsets.py |
229 |
165 |
0 |
28% |
| test/lib/python3.6/site-packages/django/forms/models.py |
676 |
490 |
0 |
28% |
| test/lib/python3.6/site-packages/django/forms/renderers.py |
35 |
9 |
0 |
74% |
| test/lib/python3.6/site-packages/django/forms/utils.py |
103 |
64 |
0 |
38% |
| test/lib/python3.6/site-packages/django/forms/widgets.py |
621 |
374 |
0 |
40% |
| test/lib/python3.6/site-packages/django/http/__init__.py |
4 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/http/cookie.py |
47 |
37 |
0 |
21% |
| test/lib/python3.6/site-packages/django/http/multipartparser.py |
379 |
322 |
0 |
15% |
| test/lib/python3.6/site-packages/django/http/request.py |
314 |
236 |
0 |
25% |
| test/lib/python3.6/site-packages/django/http/response.py |
284 |
173 |
0 |
39% |
| test/lib/python3.6/site-packages/django/middleware/__init__.py |
0 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/middleware/cache.py |
76 |
63 |
0 |
17% |
| test/lib/python3.6/site-packages/django/middleware/csrf.py |
144 |
103 |
0 |
28% |
| test/lib/python3.6/site-packages/django/shortcuts.py |
56 |
43 |
0 |
23% |
| test/lib/python3.6/site-packages/django/template/__init__.py |
10 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/template/backends/__init__.py |
0 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/template/backends/base.py |
30 |
13 |
0 |
57% |
| test/lib/python3.6/site-packages/django/template/backends/django.py |
77 |
22 |
0 |
71% |
| test/lib/python3.6/site-packages/django/template/backends/jinja2.py |
66 |
63 |
0 |
5% |
| test/lib/python3.6/site-packages/django/template/base.py |
569 |
446 |
0 |
22% |
| test/lib/python3.6/site-packages/django/template/context.py |
176 |
128 |
0 |
27% |
| test/lib/python3.6/site-packages/django/template/defaultfilters.py |
453 |
323 |
0 |
29% |
| test/lib/python3.6/site-packages/django/template/defaulttags.py |
641 |
512 |
0 |
20% |
| test/lib/python3.6/site-packages/django/template/engine.py |
118 |
58 |
0 |
51% |
| test/lib/python3.6/site-packages/django/template/exceptions.py |
12 |
8 |
0 |
33% |
| test/lib/python3.6/site-packages/django/template/library.py |
178 |
89 |
0 |
50% |
| test/lib/python3.6/site-packages/django/template/loader.py |
38 |
26 |
0 |
32% |
| test/lib/python3.6/site-packages/django/template/loader_tags.py |
198 |
157 |
0 |
21% |
| test/lib/python3.6/site-packages/django/template/response.py |
67 |
46 |
0 |
31% |
| test/lib/python3.6/site-packages/django/template/smartif.py |
107 |
64 |
0 |
40% |
| test/lib/python3.6/site-packages/django/template/utils.py |
65 |
14 |
0 |
78% |
| test/lib/python3.6/site-packages/django/templatetags/__init__.py |
0 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/templatetags/cache.py |
52 |
43 |
0 |
17% |
| test/lib/python3.6/site-packages/django/templatetags/i18n.py |
277 |
230 |
0 |
17% |
| test/lib/python3.6/site-packages/django/templatetags/l10n.py |
31 |
20 |
0 |
35% |
| test/lib/python3.6/site-packages/django/templatetags/static.py |
74 |
52 |
0 |
30% |
| test/lib/python3.6/site-packages/django/templatetags/tz.py |
79 |
57 |
0 |
28% |
| test/lib/python3.6/site-packages/django/test/__init__.py |
11 |
5 |
0 |
55% |
| test/lib/python3.6/site-packages/django/test/client.py |
356 |
269 |
0 |
24% |
| test/lib/python3.6/site-packages/django/test/html.py |
169 |
131 |
0 |
22% |
| test/lib/python3.6/site-packages/django/test/runner.py |
355 |
171 |
0 |
52% |
| test/lib/python3.6/site-packages/django/test/signals.py |
122 |
92 |
0 |
25% |
| test/lib/python3.6/site-packages/django/test/testcases.py |
694 |
474 |
0 |
32% |
| test/lib/python3.6/site-packages/django/test/utils.py |
483 |
287 |
0 |
41% |
| test/lib/python3.6/site-packages/django/urls/__init__.py |
5 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/urls/base.py |
102 |
77 |
0 |
25% |
| test/lib/python3.6/site-packages/django/urls/exceptions.py |
6 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/urls/resolvers.py |
306 |
193 |
0 |
37% |
| test/lib/python3.6/site-packages/django/urls/utils.py |
33 |
26 |
0 |
21% |
| test/lib/python3.6/site-packages/django/utils/__init__.py |
0 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/utils/_os.py |
46 |
21 |
0 |
54% |
| test/lib/python3.6/site-packages/django/utils/autoreload.py |
202 |
159 |
0 |
21% |
| test/lib/python3.6/site-packages/django/utils/baseconv.py |
48 |
25 |
0 |
48% |
| test/lib/python3.6/site-packages/django/utils/cache.py |
192 |
156 |
0 |
19% |
| test/lib/python3.6/site-packages/django/utils/crypto.py |
87 |
65 |
0 |
25% |
| test/lib/python3.6/site-packages/django/utils/datastructures.py |
176 |
98 |
0 |
44% |
| test/lib/python3.6/site-packages/django/utils/dateformat.py |
197 |
137 |
0 |
30% |
| test/lib/python3.6/site-packages/django/utils/dateparse.py |
53 |
40 |
0 |
25% |
| test/lib/python3.6/site-packages/django/utils/dates.py |
9 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/utils/datetime_safe.py |
58 |
42 |
0 |
28% |
| test/lib/python3.6/site-packages/django/utils/deconstruct.py |
24 |
9 |
0 |
62% |
| test/lib/python3.6/site-packages/django/utils/decorators.py |
102 |
55 |
0 |
46% |
| test/lib/python3.6/site-packages/django/utils/deprecation.py |
79 |
24 |
0 |
70% |
| test/lib/python3.6/site-packages/django/utils/duration.py |
26 |
22 |
0 |
15% |
| test/lib/python3.6/site-packages/django/utils/encoding.py |
110 |
57 |
0 |
48% |
| test/lib/python3.6/site-packages/django/utils/formats.py |
137 |
112 |
0 |
18% |
| test/lib/python3.6/site-packages/django/utils/functional.py |
212 |
77 |
0 |
64% |
| test/lib/python3.6/site-packages/django/utils/html.py |
183 |
135 |
0 |
26% |
| test/lib/python3.6/site-packages/django/utils/html_parser.py |
12 |
2 |
0 |
83% |
| test/lib/python3.6/site-packages/django/utils/http.py |
212 |
156 |
0 |
26% |
| test/lib/python3.6/site-packages/django/utils/inspect.py |
68 |
47 |
0 |
31% |
| test/lib/python3.6/site-packages/django/utils/ipv6.py |
112 |
102 |
0 |
9% |
| test/lib/python3.6/site-packages/django/utils/itercompat.py |
6 |
2 |
0 |
67% |
| test/lib/python3.6/site-packages/django/utils/log.py |
86 |
48 |
0 |
44% |
| test/lib/python3.6/site-packages/django/utils/lorem_ipsum.py |
29 |
20 |
0 |
31% |
| test/lib/python3.6/site-packages/django/utils/lru_cache.py |
106 |
104 |
0 |
2% |
| test/lib/python3.6/site-packages/django/utils/module_loading.py |
95 |
62 |
0 |
35% |
| test/lib/python3.6/site-packages/django/utils/numberformat.py |
45 |
39 |
0 |
13% |
| test/lib/python3.6/site-packages/django/utils/regex_helper.py |
193 |
178 |
0 |
8% |
| test/lib/python3.6/site-packages/django/utils/safestring.py |
72 |
41 |
0 |
43% |
| test/lib/python3.6/site-packages/django/utils/six.py |
451 |
204 |
0 |
55% |
| test/lib/python3.6/site-packages/django/utils/synch.py |
56 |
39 |
0 |
30% |
| test/lib/python3.6/site-packages/django/utils/termcolors.py |
57 |
40 |
0 |
30% |
| test/lib/python3.6/site-packages/django/utils/text.py |
219 |
166 |
0 |
24% |
| test/lib/python3.6/site-packages/django/utils/timesince.py |
40 |
31 |
0 |
22% |
| test/lib/python3.6/site-packages/django/utils/timezone.py |
104 |
59 |
0 |
43% |
| test/lib/python3.6/site-packages/django/utils/translation/__init__.py |
136 |
58 |
0 |
57% |
| test/lib/python3.6/site-packages/django/utils/translation/trans_real.py |
277 |
141 |
0 |
49% |
| test/lib/python3.6/site-packages/django/utils/tree.py |
49 |
18 |
0 |
63% |
| test/lib/python3.6/site-packages/django/utils/version.py |
41 |
14 |
0 |
66% |
| test/lib/python3.6/site-packages/django/utils/xmlutils.py |
16 |
9 |
0 |
44% |
| test/lib/python3.6/site-packages/django/views/__init__.py |
2 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/views/debug.py |
291 |
243 |
0 |
16% |
| test/lib/python3.6/site-packages/django/views/decorators/__init__.py |
0 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/views/decorators/cache.py |
27 |
18 |
0 |
33% |
| test/lib/python3.6/site-packages/django/views/decorators/csrf.py |
27 |
9 |
0 |
67% |
| test/lib/python3.6/site-packages/django/views/decorators/debug.py |
21 |
13 |
0 |
38% |
| test/lib/python3.6/site-packages/django/views/generic/__init__.py |
8 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/django/views/generic/base.py |
108 |
57 |
0 |
47% |
| test/lib/python3.6/site-packages/django/views/generic/dates.py |
320 |
216 |
0 |
32% |
| test/lib/python3.6/site-packages/django/views/generic/detail.py |
80 |
54 |
0 |
32% |
| test/lib/python3.6/site-packages/django/views/generic/edit.py |
116 |
66 |
0 |
43% |
| test/lib/python3.6/site-packages/django/views/generic/list.py |
99 |
66 |
0 |
33% |
| test/lib/python3.6/site-packages/django/views/i18n.py |
180 |
138 |
0 |
23% |
| test/lib/python3.6/site-packages/django/views/static.py |
62 |
45 |
0 |
27% |
| test/lib/python3.6/site-packages/pytz/__init__.py |
196 |
120 |
0 |
39% |
| test/lib/python3.6/site-packages/pytz/exceptions.py |
6 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/pytz/lazy.py |
100 |
59 |
0 |
41% |
| test/lib/python3.6/site-packages/pytz/tzfile.py |
77 |
66 |
0 |
14% |
| test/lib/python3.6/site-packages/pytz/tzinfo.py |
178 |
126 |
0 |
29% |
| test/lib/python3.6/site-packages/registration/__init__.py |
11 |
9 |
0 |
18% |
| test/lib/python3.6/site-packages/registration/auth_urls.py |
4 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/registration/auth_urls_classes.py |
6 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/registration/backends/__init__.py |
0 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/registration/backends/simple/__init__.py |
0 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/registration/backends/simple/urls.py |
4 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/registration/backends/simple/views.py |
13 |
6 |
0 |
54% |
| test/lib/python3.6/site-packages/registration/forms.py |
39 |
19 |
0 |
51% |
| test/lib/python3.6/site-packages/registration/signals.py |
3 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/registration/validators.py |
37 |
14 |
0 |
62% |
| test/lib/python3.6/site-packages/registration/views.py |
43 |
23 |
0 |
47% |
| test/lib/python3.6/site-packages/tinymce/__init__.py |
0 |
0 |
0 |
100% |
| test/lib/python3.6/site-packages/tinymce/models.py |
15 |
2 |
0 |
87% |
| test/lib/python3.6/site-packages/tinymce/settings.py |
19 |
4 |
0 |
79% |
| test/lib/python3.6/site-packages/tinymce/widgets.py |
102 |
68 |
0 |
33% |


{% extends "base.html" %} {% block title %}Template Syntax{% endblock %} {% block content %}
The configuration templates are parsed by a Mako Template Engine. The Web service doesn't restrict the content of the templates, therefore almost every feature that is part of the Mako Template Engine can be used, except multiple files for the rendering process. Please note that the following Syntax is tested during the development process.
The following example is a plain configuration template with four variables.
! hostname ${ hostname } ! interface ${ management_interface } ip address ${ management_ip } ${ management_subnetmask } !
The parser within the Config Template data object will automatically detect these variables and save it to the database.
hostname
variable is always created and contains always the name of the
Template Value Set.
${
and }
.
The following configuration template contains a simple if/else control structure that checks if a variable is defined.
% if var: variable defined % else: variable is not defined % endif
The template engine allows the use of comments, which are not part of the resulting configuration. The following example contains single line comments.
## Some introduction that is not part of the resulting configuration ! hostname ${ hostname } ! interface ${ management_interface } ip address ${ management_ip } ${ management_subnetmask } !
The following example contains multiline comments.
<%doc> Some introduction that is not part of the resulting configuration There are more detailed explanations possible. </%doc> ! hostname ${ hostname } ! interface ${ management_interface } ip address ${ management_ip } ${ management_subnetmask } !{% endblock %}


This brief rummage through the Hooting Yard postbag ends with the following, from reader Peter Ross:
While in Norfolk we went to something called ‘The Village Experience’. It was like a League of Gentlemen version of Legoland. Each of the so called rides, which only functioned every hour or so, was attended by a humpbacked man with a limp. There was also a large shed containing a Wurlitzer collection where we managed to catch a concert performed by a slightly odd teenager. The whole place looked like it had been built in the 1960s and never updated. In fact it would not have surprised me if the whole thing had been brought over from Plovdiv. Don't know why I have told you this, except that it had a certain Hooting Yard quality about it. Sadly the place is closing down in September.


Enter your email and get the magical file emailed to you! (Optional)
Enter a valid email.
{{message}}


Security Model
Introduction
The Service APIs have been designed to enable granular authorization for each role in a typical organization.
Resources
The Service APIs have 3 primary API resources:
- GatewayClass defines a set of gateways with a common configuration and behavior.
- Gateway requests a point where traffic can be translated to Services within the cluster.
- Routes describe how traffic coming via the Gateway maps to the Services.
Additional Configuration
There are two additional pieces of configuration that are important in this security model:
- Which namespaces can contain Gateways of the specified GatewayClass.
- Which namespaces Routes can be targeted in by Gateways of the specified GatewayClass.
Roles
For the purposes of this security model, 3 common roles have been identified:
- Infrastructure provider: The infrastructure provider (infra) is responsible for the overall environment that the cluster(s) are operating in. Examples include: the cloud provider (AWS, Azure, GCP, ...), the PaaS provider in a company.
- Cluster operator: The cluster operator (ops) is responsible for administration of entire clusters. They manage policies, network access, application permissions.
- Application developer: The application developer (dev) is responsible for defining their application configuration (e.g. timeouts, request matching/filter) and Service composition (e.g. path routing to backends).
Although these roles can cover a wide variety of use cases, some organizations may be structured slightly differently. Many organizations may also have a fourth role that sits between "cluster operator" and "application developer":
- Application admin: The application admin has administrative access to some namespaces within a cluster, but not the cluster as a whole.
The Security Model
There are two primary components to the Service APIs security model: RBAC and namespace restrictions.
RBAC
RBAC (role-based access control) is the standard used for Kubernetes authorization. This allows users to configure who can perform actions on resources in specific scopes. RBAC can be used to enable each of the roles defined above. In most cases, it will be desirable to have all resources be readable by most roles, so instead we'll focus on write access for this model.
Write Permissions for Simple 3 Tier Model
| GatewayClass | Gateway | Route | |
|---|---|---|---|
| Infrastructure Provider | Yes | Yes | Yes |
| Cluster Operators | No | Yes | Yes |
| Application Developers | No | No | Yes |
Write Permissions for Advanced 4 Tier Model
| GatewayClass | Gateway | Route | |
|---|---|---|---|
| Infrastructure Provider | Yes | Yes | Yes |
| Cluster Operators | Sometimes | Yes | Yes |
| Application Admins | No | In Specified Namespaces | In Specified Namespaces |
| Application Developers | No | No | In Specified Namespaces |
Namespace Restrictions
The extra configuration options are not possible to control with RBAC. Instead, they will be controlled with configuration fields on GatewayClasses:
-
allowedGatewayNamespaceSelector: This field is a selector of namespaces that Gateways can use this GatewayClass from. This is a standard Kubernetes LabelSelector, a label query over a set of resources. The result of matchLabels and matchExpressions are ANDed. Controllers must not support Gateways in namespaces outside this selector. An empty selector (default) indicates that Gateways can use this GatewayClass from any namespace. This field is intentionally not a pointer because the nil behavior (no namespaces) is undesirable here.
-
allowedRouteNamespaces: AllowedRouteNamespaces indicates in which namespaces Routes can be selected for Gateways of this class. This is restricted to the namespace of the Gateway by default.
Controller Requirements
To be considered conformant with the Service APIs spec, controllers need to:
- Populate status fields on Gateways and Resources to indicate if they are compatible with the corresponding GatewayClass configuration.
- Not implement invalid configuration. Fore example, if a route is referenced in an invalid namespace for the GatewayClass, it should be ignored.
- Respond to changes in GatewayClass configuration that may change which Gateways or Routes are valid.
Alternative Approaches Considered
New API Resources
We considered introducing new API resources to cover these use cases. These resources might be look something like:
- ClusterGateway: A ClusterGateway could reference routes in any namespace.
- ClusterRoute: A ClusterRoute could be referenced by any Gateway or ClusterGateway.
Benefits
- Easy to model with RBAC.
- API validation tied directly to each resource.
Downsides
- New resources to deal with - more informers, clients, documentation, etc.
- Harder to expand with additional options in the future - may just end up with tons of API resources to cover all use cases.
Boolean Multi Namespace Route Indicator on GatewayClass
Instead of having the routeNamespaceSelector
field on GatewayClass, we would
use a boolean multiNamespaceRoutes
field to indicate if Gateways of this class
can target routes in multiple namespaces. This would default to false. A false
value here would indicate that routes could only be targeted in the current
namespace.
Benefits
- Helpful for multi-tenant use cases with many isolated Gateways.
- Simple configuration with an easy to understand default value.
Downsides
- GatewayClass admins are unable to partially limit namespaces that can be targeted by Gateways. Admins would have to choose between allowing access to Routes in all namespaces or only the local one.
Validating Webhook
A validating webhook could potentially handle some of the cross-resource validation necessary for this security model and provide more immediate feedback to end users.
Benefits
- Immediate validation feedback.
- More validation logic stays in core Service APIs codebase.
Downsides
- Imperfect solution for cross-resource validation. For example, a change to a GatewayClass could affect the validity of corresponding Gateway.
- Additional complexity involved in installing Service APIs in a cluster.


Dashi
Toggle navigation
Dashi on GitHub
Page Header
Optional description
Level
Here
Yearly Performance
(radius: fluctuation/index ratio, color: gain/loss)
reset
Days by Fluctuation(%)
reset
Day of Week
reset
Quarters
reset
Days by Gain/Loss
reset
Monthly Index Abs Move & Volume/500,000 Chart
range:
reset


--- layout: trainup title: The Data Unit short: Who works with data, and how? image: trainup.jpg ---
Part of our collection of basic data literacy content
{% include social_sharing.html %}The skills that are necessary to commit responsible storytelling on data, range between data processing, journalism, coding, and design.
An ideal team of individuals, known as the data unit, who perform data storytelling, is composed of professionals such as data wranglers, storytellers, developers, editors and designers.
Each member of the data unit possesses a different skillset. The data unit acts as a team, with individual strengths contributing to the overall output. The data unit is largely without hierarchy, and every member’s contribution is equally as important and necessary as any other member’s in order to complete the objectives set out by each stage of the data pipeline.
Thus members must work together and collaborate in the decision-making processes in order to progress the storytelling.
“There’s a digital revolution taking place both in and out of government in favor of open-sourced data, innovation, and collaboration.”
- Kathleen Sebelius, Former United States Secretary of Health and Human Services
There may be many challenges an organisation or team will face in terms of a shortage of available or permanent resources, or capacity. Realistically, not every company, organisation, or individual will be able to establish a full-scale data unit.
Yet there are many ways in which the data unit can be materialised in order to suit the resources available to the company, organisation, or individual. To help with this, there are two perspectives from which you can view the data unit. The perspective you choose is dependent on what best supports your current circumstance.
Data storytelling is made possible through investing in networks, connections and associations, leveraging resources and tapping into the existing online community where you can always find a way to simulate or develop a particular skill or competency, or find someone who can help out with a task you may not be able to cover in-house.
It is important to note that the size of the data unit does not prevent an individual, company or organisation from successfully telling stories with data.
The jack of all trades is a lone ranger. From data sourcing to cleaning, analysis and visualisation. Alone, this one-man data unit completes every task along the data pipeline. And the Open Movement has a lot to do with the jack of all trades’ ability to do so.
The international drive towards ‘openness’ has not only made the sourcing of data much easier, but has also been the driving force behind the development of many of the tools that make the cleaning, processing and visualisation of data possible - without the need to be an expert in any single part of the process.
Below are some examples of the way in which the data liberation has made it easier for the jack of all trades to work alone:
|
Sourcing |
Open Government and Open Data initiatives |
|
Cleaning |
OpenRefine, Google Sheets and more. |
|
Analysis |
Google Sheets, LibreOffice, Tableau Public and more. |
|
Visualisation |
Datawrapper, Charted, RAWGraphs, Tableau Public, Carto (for map-based visualisation), Google DataStudio, KnightLab Storytelling Tools, Piktochart, Infogr.am and more. |
The large-scale data unit includes all the roles required for storytelling with data. Large-scale teams often have a long-term vision that includes opportunity for long form investigative stories, shorter projects as well as experimentation of methods and techniques.
Thus this data unit is not solely focused on data storytelling but also dedicated to progressing or advancing the field of data storytelling, data liberation and open-source.
You can see examples of large-scale data units at The Guardian, La Nación and Australian Broadcasting Corporation (ABC), and the BBC.
The Data Unit is best understood by the different roles that need to be fulfilled. The typical roles that make up a data unit are:
But what do they actually do? Let’s look at each role in light of their tasks and competencies.
The project manager oversees the management of the complete process from ideation to publication and distribution.
Data wrangling is the most impactful step in the data pipeline.
This is because every other role within the unit is, to a significant degree, dependent on the output of the data wrangler in order to move ahead.
The storyteller conducts the journalism on the numbers. The role of the storyteller is not only to dig around in the data to find the stories, but to go out into the world to see if those stories hold true i.e. conduct reporting on the data.
Remember the numbers are not the story, just the source of the story. The storyteller will still have to go out, report on it, and weave together a story that best captures the message.
Data storytelling, often digitally-driven, presents the need for the inclusion of a developer in the unit who assists with the technical elements of the project. These technical elements can take on the form of data visualisations, storytelling templates, data-driven tools and web applications.
Ideally, the developer in this case should also possess a basic understanding and basic working proficiency in visual communication and design.
Collaboration is defined as the action of working with someone to produce something and the success of the data unit is dependent on each member’s ability to work collaboratively.
But what does it mean to collaborate? And how far does this collaboration extend into the workflow of each of the individual roles making up the data unit?
In order to collaborate effectively as a member of the data unit, or merely to context-switch between skills when working alone, there are a few things you need to consider before getting started:
It is critical that each member of the data unit understands something of the function of the others. Without this understanding, as a member of the data unit, you will be unaware of what each member needs from you and when they need it, or when you will receive what you need from the others.
Different technical skills follow different processes and need to uphold different standards in the fulfilment of their tasks. The workflow for each member in the completion of their objective is different and it may be some time before they are able to deliver the output that another member requires in order to move forward.
Almost all decision-making during the course of the project is done collaboratively. The expertise of every member in collaboration with other members is needed to progress and shape the project. Often, the work of one member is prepared and completed to suit the needs and requirements of the member (or competency) to follow. And this informs the fundamental mode for collaboration.
What does collaboration look like and what process does it follow?
The project manager is assigned to a project, in this instance the project is a data-driven story. The project manager then assembles a team together.
The project is introduced to the team. The team members, while leveraging their collective expertise, shape the agenda of the project, determine a timeline that works in conjunction with an estimation of assumed tasks and knowledge of individual workflows, as well as bearing in mind the scale of the project itself.
Once the agenda has been set, the project manager is responsible for allocating resources and capacity (human and other), as well as acquiring that which is not available internally, in order to see the fulfillment of the project at hand.
At times, when kicking off a data story, you will find that you begin so in possession of a dataset. In the event that this is not the case, the relevant data to pair with the agenda set by the project manager in collaboration with the team, will have to be sourced.
The act of sourcing data includes both finding the data and getting the data. In terms of the data unit, this is often done by the the storyteller, or the data wrangler, or both. This is often dependent on the competencies that either of these individuals possess.
At times the storyteller will have nurtured the correct relationships and contacts to source the relevant data directly through domain experts, or data custodians, or be familiar with various data portals and other online sources of information. Whereas the data wrangler may be more skilled in actually getting the data, by means of download and scraping, or pulling it in from an API, while making sure that it is in a machine-readable format that can be cleaned and analysed.
The storyteller may be more skilled in the process of verification when it comes to content-related aspects, while the data wrangler may prove more efficient in verifying the dataset itself, uncovering the source of the data, and authoring the data profile.
Once these two members of the data unit are satisfied with the data they have, the data wrangler can proceed to clean the data and structure it for analysis.
This next stage is performed by the data wrangler. Data can only be mined for stories once it has been cleaned and structured for analysis. Cleaning the data involves getting rid of data errors, false positives, removing or redefining empty cells and duplicates, correcting inconsistencies in spelling or the presentation of the data, applying the correct formatting to different data types, spotting and understanding the outliers, and much more.
Any one act of data cleaning involves two processes: (1) the detection and (2) the correction of a data entry (or a group of data entries). Depending on the size and quality of a dataset, data cleaning can often be the most time consuming task for thea data wrangler to perform. Only with clean and correctly structured data is the data wrangler able to proceed with the initial exploratory analysis and interpretation of the data.
Note, the data wrangler will also structure the data bearing in mind the objectives of the project, as established by the project team.
Analysis happens in two stages and committedly involves both the data wrangler and the storyteller.
Firstly, with the data cleaned, the data wrangler is able to execute the initial exploratory analysis and interpretation of the data. This process seeks to uncover the type of information contained within the dataset, while surveying the opportunities available for storytelling. Additionally, the data wrangler also considers different ways in which the data can be grouped, and what these groupings say about the dataset or topic as a whole.
The data wrangler will feedback the initial findings to the rest of the data unit. The data wrangler will need the storyteller’s eye and investigative integrity to lead the next leg of analysis – that is, mining for stories.
Based on the findings that are presented by the data wrangler to the storyteller, the storyteller will, both alone and in collaboration with the data wrangler, develop a selection of critical or core questions with which to interview the data. The data wrangler will use this as a guide to process the data and dig for answers. These answers, which will be presented in the form of data points will act as a springboard from which the storyteller will begin shaping the data story.
Now that the data has been mined for storytelling, and various insights have been lifted from the dataset(s), the storyteller can begin their job of bringing the story to life.
In order to communicate and build relevance around the information contained within a dataset, the storyteller must first reach out to the key stakeholders around whom the story centres. It is the storyteller’s role to discover whether the data holds true to the real world and understand the ways in which the data, and its interpretation, will benefit or enrich those for whom the story would have the highest impact. Outliers, peaks, trends and variances found in the data need to be investigated and reported in the same way as any other story leads.
The storyteller will report on the data and ask relevant stakeholders questions surrounding the insights garnered from the data. After this, the storyteller will take this newly acquired information, return to the data and assess the information in the context of the dataset and vice versa. This process of alignment is one of the critical stages in beginning to shape the data story.
At this point you would bring the data wrangler and project manager back into the fold and begin to further develop and carve a story out of the resources, reporting, and data insights acquired up until this point.
Lastly, the developer/designer will be brought in and updated regarding the direction of the story and to begin brainstorming possibilities for the visualisation or presentation of the data, and the story as a whole.
When we talk about package and present, we are referring to the final stage in the processing of a dataset. Packaging and presenting the data story includes the story map, which is the blueprint for how the different elements should be structured in order to convey the final message. These different elements could include different combinations of written content, data visualisations, as well as any graphics, photographs or other multimedia elements.
This process is collaborated on by the storyteller and the developer/designer, while being overseen by the project manager. Initially, the storyteller and developer/designer will plan the presentation of the story. Together they will define the layout and storymap, meaning they will determine what elements will be positioned at which points along the story, how the various elements will interact with one another, whether the representation of the data in its various forms throughout the story is cohesive in its efforts to convey the data insights guiding the story, and assess the ways in which these elements, and data points, may enrich or distract audience members in their following of the story. This session will be fed back to the project manager, and once approved, the developer/designer will proceed to implement the storymap.
In terms of visualising the data, the developer/designer will consult the data wrangler during this phase in order to get access to the relevant data and discuss and share ideas around the ways in which the data is best presented. The storyteller will review the work in terms of its relation to the written content, while the project manager will continue to oversee the entire process, making sure ethical guidelines and publication standards are upheld.
The developer/designer in this case is responsible for packaging the final product to suit online and offline publication.
This curriculum has been developed by OpenUp.
That's great to hear! We want to make it even better and could really use your feedback.
How will you apply what you learned?
You are free to use, share, and adapt this content to your needs. Do you want to teach others? Let us know how we can help.
We're sorry to hear that.
Please let us know how we can improve.


This is part of the old website. New website begins at fontforge.github.io
Are you a web developer? Help us migrate this page on Github
If you open a truetype font containing bitmaps then you will be asked if you want to load some of the bitmaps as well as the outlines.
By default this dialog will display all files with extensions of pfa, pfb,
pt3, sfd, ttf, otf, otb, t42, cef, cff, gsf, ttc, svg, ik, mf and bdf (possibly
others as FontForge comes to support more formats). You can change this with
the Filter pull down list -- there are several standard filters, and you
may define your own.
You may select multiple files (by holding down the shift or control keys
when clicking on them), and all selected files will be opened.
FontForge can open macbinary resource files containing postscript and truetype
fonts (it does not open bitmap fonts currently)
FontForge does not open Acorn RISC/OS files, but you can use
acorn2sfd to convert them into an sfd
file which FontForge can then open.
If you have mf and
autotrace
installed on your machine FontForge will process metafont's mf files
for you. But you might want to use pktrace, mftrace or some other
standalone program to do the job.
When opening a TTC file, or a mac dfont -- files which potentially contain
several fonts -- you will be given a dlg showing a list of all fonts in the
file, you get to pick which you want to open. (FontForge does not provide
a way to open all fonts in a file at once). If you know the fontname you
are interested in you may append it to the filename in the open dlg as:
Helvetica.dfont(Helvetica Bold)
or if you know the font index
Helvetica.dfont(0)
(indeces start at 0, not 1).
When FontForge opens a pdb file (one that contains palm bitmap fonts) it will open the first font it finds. In most formats it will list the available fonts in a file and ask which you want, but palm fonts contain no fontname so there is no way to identify them.
When importing a type3 font FontForge will ask you a few questions. It shouldn't have to ask these questions, but this is an imperfect world and FontForge an imperfect program. In some rare cases FontForge will crash if it tries to do a remove overlap. The remove overlap functionality is important for interpreting stroked paths so you really should have it on. But if a crash happens then, turn it off (and the crash should not repeat, but some functionality will be lost).
Not all font formats that fontforge supports have standard extensions. Mac resource forks are one example, postscript cid, type0 and type3 fonts are another. FontForge can still open these formats, even if it fails to display the file. You can always type the file name in yourself if you don't see it in the file list.
FontForge can also read (many) fonts out of a pdf file. FontForge usually does not list pdf files (because they aren't really designed as mechanisms for transporting fonts and most such fonts will be incomplete due to subsetting and other optimizations), but you can always type in the name of one directly (or use the [Filter] button to define a filter for pdf files).
You can also force fontforge to rename all the glyphs in the font being read in to fit some standard naming convention. See the section on namelists for more information.
If this is a font view and the font has been changed, then it will ask whether you want to save the font. It will also close any outline glyph, bitmap glyph or metrics views associated with the font.
If you are editing a font "Ambrosia.sfd" then the backup file will be called "Ambrosia.sfd~".
So if you have changed the name of the glyph this command will fail.
If the font did not come from an sfd file this command will fail.
If the font has been reencoded and the glyph has references this command
may fail.
If you have made a global change to the font (like scaling it to a new em-size)
then the results may not be appropriate.
In the Bitmap view this allows you to export the current glyph as either a .xbm or a .bmp (always as a bitmap) file.
This menu item is not available in the Font or Metrics Views.
If you are editing a multi-layered font (and have a version of FontForge configured for it) then you can also import an image into one of the foreground layers.
FontForge does best when given bitmap images. It will grey out the foreground and make the background transparent. It will also compress them when it stores them in the sfd file. It will handle most other image formats but does not try to optimize them in anyway. Please use bitmaps here.
You may load an encapsulated postscript file (or rather the sub-set of postscript
that FontForge understands) into the foreground of glyphs. As with images
above this may import either depending on the selection or a template.
If you have libxml2 on your system then FontForge will also be able to import
svg files. As with postscript, only a subset of svg is understood).
In the Outline View this allows you to import an image into the background (see the above remark about bitmaps, or import eps or fig files into the foreground (the xfig conversion is really bad, the eps conversion is very limited).
In the Bitmap View this allows you to import a bitmap image into the glyph.
This menu item is not available in the Metrics View
In the font view you may select multiple files (by holding down the shift
or control keys when clicking on them), and all selected bitmap fonts will
be imported into the sfd.
Note: When loading a postscript font from a mac resource file, the associated kerning data will be found in the FOND stored with a bitmap font for this face. FontForge can't guess the name of this file when loading the font. You must figure it out yourself.
A number of things, like the colors used in FontForge, that might be controlled from a preference window are controlled by X Resources below.


{{ define "main" }} Chen Ning Student and aspiring software engineer. Blog {{ partial "blog-feed.html" . }} Projects {{ end }}
Student and aspiring software engineer.


Actions, resources, and condition keys for Amazon Nimble Studio
Amazon Nimble Studio (service prefix:
nimble
) provides the following service-specific resources, actions, and condition context keys for use in IAM permission policies.
References:
-
Learn how to configure this service .
-
View a list of the API operations available for this service .
-
Learn how to secure this service and its resources by using IAM permission policies.
Topics
Actions defined by Amazon Nimble Studio
You can specify the following actions in the
Action
element of an IAM policy statement. Use policies to grant permissions to perform an operation in AWS. When you use an action in a policy, you usually allow or deny access to the API operation or CLI command with the same name. However, in some cases, a single action controls access to more than one operation. Alternatively, some operations require several different actions.
The
Resource types
column of the Actions table indicates whether each action supports resource-level permissions. If there is no value for this column, you must specify all resources ("*") to which the policy applies in the
Resource
element of your policy statement. If the column includes a resource type, then you can specify an ARN of that type in a statement with that action. If the action has one or more required resources, the caller must have permission to use the action with those resources. Required resources are indicated in the table with an asterisk (*). If you limit resource access with the
Resource
element in an IAM policy, you must include an ARN or pattern for each required resource type. Some actions support multiple resource types. If the resource type is optional (not indicated as required), then you can choose to use one of the optional resource types.
The
Condition keys
column of the Actions table includes keys that you can specify in a policy statement's
Condition
element. For more information on the condition keys that are associated with resources for the service, see the
Condition keys
column of the Resource types table.
For details about the columns in the following table, see Actions table .
| Actions | Description | Access level | Resource types (*required) | Condition keys | Dependent actions |
|---|---|---|---|---|---|
| AcceptEulas | Grants permission to accept EULAs | Write | |||
| CreateLaunchProfile | Grants permission to create a launch profile | Write |
ec2:CreateNetworkInterface ec2:DescribeNatGateways ec2:DescribeNetworkAcls ec2:DescribeRouteTables ec2:DescribeSubnets ec2:DescribeVpcEndpoints ec2:RunInstances |
||
| CreateStreamingImage | Grants permission to create a streaming image | Write |
ec2:DescribeImages ec2:DescribeSnapshots ec2:ModifyInstanceAttribute ec2:ModifySnapshotAttribute ec2:RegisterImage |
||
| CreateStreamingSession | Grants permission to create a streaming session | Write |
ec2:CreateNetworkInterface ec2:CreateNetworkInterfacePermission nimble:GetLaunchProfile nimble:GetLaunchProfileInitialization nimble:ListEulaAcceptances |
||
| CreateStreamingSessionStream | Grants permission to create a StreamingSessionStream | Write | |||
| CreateStudio | Grants permission to create a studio | Write |
iam:PassRole sso:CreateManagedApplicationInstance |
||
| CreateStudioComponent | Grants permission to create a studio component. A studio component designates a network resource to which a launch profile will provide access | Write |
ds:AuthorizeApplication ds:DescribeDirectories ec2:DescribeSecurityGroups fsx:DescribeFileSystems iam:PassRole |
||
| DeleteLaunchProfile | Grants permission to delete a launch profile | Write | |||
| DeleteLaunchProfileMember | Grants permission to delete a launch profile member | Write | |||
| DeleteStreamingImage | Grants permission to delete a streaming image | Write |
ec2:DeleteSnapshot ec2:DeregisterImage ec2:ModifyInstanceAttribute ec2:ModifySnapshotAttribute |
||
| DeleteStreamingSession | Grants permission to delete a streaming session | Write |
ec2:DeleteNetworkInterface |
||
| DeleteStudio | Grants permission to delete a studio | Write |
sso:DeleteManagedApplicationInstance |
||
| DeleteStudioComponent | Grants permission to delete a studio component | Write |
ds:UnauthorizeApplication |
||
| DeleteStudioMember | Grants permission to delete a studio member | Write | |||
| GetEula | Grants permission to get a EULA | Read | |||
| GetFeatureMap [permission only] | Grants permission to allow Nimble Studio portal to show the appropriate features for this account | Read | |||
| GetLaunchProfile | Grants permission to get a launch profile | Read | |||
| GetLaunchProfileDetails | Grants permission to get a launch profile's details, which includes the summary of studio components and streaming images used by the launch profile | Read | |||
| GetLaunchProfileInitialization | Grants permission to get a launch profile initialization. A launch profile initialization is a dereferenced version of a launch profile, including attached studio component connection information | Read |
ds:DescribeDirectories ec2:DescribeSecurityGroups fsx:DescribeFileSystems |
||
| GetLaunchProfileMember | Grants permission to get a launch profile member | Read | |||
| GetStreamingImage | Grants permission to get a streaming image | Read | |||
| GetStreamingSession | Grants permission to get a streaming session | Read | |||
| GetStreamingSessionBackup | Grants permission to get a streaming session backup | Read | |||
| GetStreamingSessionStream | Grants permission to get a streaming session stream | Read | |||
| GetStudio | Grants permission to get a studio | Read | |||
| GetStudioComponent | Grants permission to get a studio component | Read | |||
| GetStudioMember | Grants permission to get a studio member | Read | |||
| ListEulaAcceptances | Grants permission to list EULA acceptances | Read | |||
| ListEulas | Grants permission to list EULAs | Read | |||
| ListLaunchProfileMembers | Grants permission to list launch profile members | Read | |||
| ListLaunchProfiles | Grants permission to list launch profiles | Read | |||
| ListStreamingImages | Grants permission to list streaming images | Read | |||
| ListStreamingSessionBackups | Grants permission to list streaming session backups | Read | |||
| ListStreamingSessions | Grants permission to list streaming sessions | Read | |||
| ListStudioComponents | Grants permission to list studio components | Read | |||
| ListStudioMembers | Grants permission to list studio members | Read | |||
| ListStudios | Grants permission to list all studios | Read | |||
| ListTagsForResource | Grants permission to list all tags on a Nimble Studio resource | Read | |||
| PutLaunchProfileMembers | Grants permission to add/update launch profile members | Write |
sso-directory:DescribeUsers |
||
| PutStudioLogEvents [permission only] | Grants permission to report metrics and logs for the Nimble Studio portal to monitor application health | Write | |||
| PutStudioMembers | Grants permission to add/update studio members | Write |
sso-directory:DescribeUsers |
||
| StartStreamingSession | Grants permission to start a streaming session | Write |
nimble:GetLaunchProfile nimble:GetLaunchProfileMember |
||
| StartStudioSSOConfigurationRepair | Grants permission to repair the studio's AWS IAM Identity Center configuration | Write |
sso:CreateManagedApplicationInstance sso:GetManagedApplicationInstance |
||
| StopStreamingSession | Grants permission to stop a streaming session | Write |
nimble:GetLaunchProfile |
||
| TagResource | Grants permission to add or overwrite one or more tags for the specified Nimble Studio resource | Tagging | |||
| UntagResource | Grants permission to disassociate one or more tags from the specified Nimble Studio resource | Tagging | |||
| UpdateLaunchProfile | Grants permission to update a launch profile | Write |
ec2:DescribeNatGateways ec2:DescribeNetworkAcls ec2:DescribeRouteTables ec2:DescribeSubnets ec2:DescribeVpcEndpoints |
||
| UpdateLaunchProfileMember | Grants permission to update a launch profile member | Write | |||
| UpdateStreamingImage | Grants permission to update a streaming image | Write | |||
| UpdateStudio | Grants permission to update a studio | Write |
iam:PassRole |
||
| UpdateStudioComponent | Grants permission to update a studio component | Write |
ds:AuthorizeApplication ds:DescribeDirectories ec2:DescribeSecurityGroups fsx:DescribeFileSystems iam:PassRole |
Resource types defined by Amazon Nimble Studio
The following resource types are defined by this service and can be used in the
Resource
element of IAM permission policy statements. Each action in the
Actions table
identifies the resource types that can be specified with that action. A resource type can also define which condition keys you can include in a policy. These keys are displayed in the last column of the Resource types table. For details about the columns in the following table, see
Resource types table
.
| Resource types | ARN | Condition keys |
|---|---|---|
| studio |
arn:$
{
Partition}:nimble:$
{
Region}:$
{
Account}:studio/$
{
StudioId}
|
|
| streaming-image |
arn:$
{
Partition}:nimble:$
{
Region}:$
{
Account}:streaming-image/$
{
StreamingImageId}
|
|
| studio-component |
arn:$
{
Partition}:nimble:$
{
Region}:$
{
Account}:studio-component/$
{
StudioComponentId}
|
|
| launch-profile |
arn:$
{
Partition}:nimble:$
{
Region}:$
{
Account}:launch-profile/$
{
LaunchProfileId}
|
|
| streaming-session |
arn:$
{
Partition}:nimble:$
{
Region}:$
{
Account}:streaming-session/$
{
StreamingSessionId}
|
|
| streaming-session-backup |
arn:$
{
Partition}:nimble:$
{
Region}:$
{
Account}:streaming-session-backup/$
{
StreamingSessionBackupId}
|
|
| eula |
arn:$
{
Partition}:nimble:$
{
Region}:$
{
Account}:eula/$
{
EulaId}
|
|
| eula-acceptance |
arn:$
{
Partition}:nimble:$
{
Region}:$
{
Account}:eula-acceptance/$
{
EulaAcceptanceId}
|
Condition keys for Amazon Nimble Studio
Amazon Nimble Studio defines the following condition keys that can be used in the
Condition
element of an IAM policy. You can use these keys to further refine the conditions under which the policy statement applies. For details about the columns in the following table, see
Condition keys table
.
To view the global condition keys that are available to all services, see Available global condition keys .
| Condition keys | Description | Type |
|---|---|---|
| aws:RequestTag/${TagKey} | Filters access by a tag key and value pair that is allowed in the request | String |
| aws:ResourceTag/${TagKey} | Filters access by a tag key and value pair of a resource | String |
| aws:TagKeys | Filters access by a list of tag keys that are allowed in the request | ArrayOfString |
| nimble:createdBy | Filters access by the createdBy request parameter or the ID of the creator of the resource | String |
| nimble:ownedBy | Filters access by the ownedBy request parameter or the ID of the owner of the resource | String |
| nimble:principalId | Filters access by the principalId request parameter | String |
| nimble:requesterPrincipalId | Filters access by the ID of the logged in user | String |
| nimble:studioId | Filters access by a specific studio | ARN |


The Harmony3 configurator already has a pin manager that lets you configure PPS pins in software. This tool is meant mainly for system and Hardware designers who want to quickly explore
the set of functionality that can be accomodated into a design using the WFI32E01 modules.
Select SoC Functions
display dedicted pins? change will be applied on next calculation
Pins available for configuration
This is a personal project created by Vysakh P Pillai. It is not affiliated with Microchip Technology


IL - Authentication at Edge return endpoint
You will be redirected to website you requested shortly. If this does not happen, contact your website's administration.


|
KratosMultiphysics
KRATOS Multiphysics (Kratos) is a framework for building parallel, multi-disciplinary simulation software, aiming at modularity, extensibility, and high performance. Kratos is written in C++, and counts with an extensive Python interface.
|
All the processes python should be derived from "Process". More...
Public Member Functions | |
| def | __init__ (self, model, settings) |
| def | Check (self) |
| def | ExecuteInitialize (self) |
| def | ExecuteFinalizeSolutionStep (self) |
| def | ExecuteFinalize (self) |
Public Attributes | |
| integration_end_time | |
| model | |
| model_part_name | |
| domain_size | |
| averaging_process_parameters | |
| metric_divergencefree_parameters | |
All the processes python should be derived from "Process".
| def divergencefree_refinement_process.DivergenceFreeRefinementProcess.__init__ | ( | self, | |
| model, | |||
| settings | |||
| ) |
| def divergencefree_refinement_process.DivergenceFreeRefinementProcess.Check | ( | self | ) |
| def divergencefree_refinement_process.DivergenceFreeRefinementProcess.ExecuteFinalize | ( | self | ) |
| def divergencefree_refinement_process.DivergenceFreeRefinementProcess.ExecuteFinalizeSolutionStep | ( | self | ) |
| def divergencefree_refinement_process.DivergenceFreeRefinementProcess.ExecuteInitialize | ( | self | ) |
| divergencefree_refinement_process.DivergenceFreeRefinementProcess.averaging_process_parameters |
| divergencefree_refinement_process.DivergenceFreeRefinementProcess.domain_size |
| divergencefree_refinement_process.DivergenceFreeRefinementProcess.integration_end_time |
| divergencefree_refinement_process.DivergenceFreeRefinementProcess.metric_divergencefree_parameters |
| divergencefree_refinement_process.DivergenceFreeRefinementProcess.model |
| divergencefree_refinement_process.DivergenceFreeRefinementProcess.model_part_name |


PerCuriam
CALIFORNIA PUBLIC EMPLOYEES RETIREMENT
SYSTEM,
et al.
, PETITIONERS
v.
PAUL FELZEN et al.
Per Curiam .
The judgment is affirmed by an equally divided Court.
Justice OConnor took no part in the consideration or decision of this case.
PerCuriam
CALIFORNIA PUBLIC EMPLOYEES RETIREMENT
SYSTEM,
et al.
, PETITIONERS
v.
PAUL FELZEN et al.
Per Curiam .
The judgment is affirmed by an equally divided Court.
Justice OConnor took no part in the consideration or decision of this case.
PerCuriam
CALIFORNIA PUBLIC EMPLOYEES RETIREMENT
SYSTEM,
et al.
, PETITIONERS
v.
PAUL FELZEN et al.
Per Curiam .
The judgment is affirmed by an equally divided Court.
Justice OConnor took no part in the consideration or decision of this case.
PerCuriam
CALIFORNIA PUBLIC EMPLOYEES RETIREMENT
SYSTEM,
et al.
, PETITIONERS
v.
PAUL FELZEN et al.
Per Curiam .
The judgment is affirmed by an equally divided Court.
Justice OConnor took no part in the consideration or decision of this case.
PerCuriam
CALIFORNIA PUBLIC EMPLOYEES RETIREMENT
SYSTEM,
et al.
, PETITIONERS
v.
PAUL FELZEN et al.
Per Curiam .
The judgment is affirmed by an equally divided Court.
Justice OConnor took no part in the consideration or decision of this case.


Pakistani Leader Blames India for Smog Problem
Pollution so bad parents told not to send kids to school
by DWRights groups called on Lahore to take “urgent action” to prevent a thick smog further engulfing the city of more than 10 million people.
Authorities told parents not to send their children to school.
Amnesty International is urging global support for a campaign on behalf of residents in Pakistan’s eastern Punjab city of Lahore where a thick smog continues to loom over the region.
The UK-based rights group warned Friday that tens of thousands of people are at risk of respiratory disease due to the poor air quality.
The warning comes a day after Lahore’s Air Quality Index skyrocketed to 598. At 300 and above, the air is considered unhealthy.
Amnesty blamed rising smog levels on the Pakistani government’s insufficient response.
“The hazardous air is putting everyone’s right to health at risk,” said Rimmel Mohydin, South Asia Campaigner at Amnesty.
“The issue is so serious that we are calling on our members around the world to write to the Pakistani authorities to tell them to stop downplaying the crisis and take urgent action to protect people’s health and lives.”
Flashback! Alex Jones Outed George Soros As A Nazi Colaborator In 2012
Originally aired January 25th, 2012, Alex Jones plays rare clips and covers the news of George Soros relishing that he worked with Nazis as a young man.
One of the Most Polluted Cities
Lahore, one of the country’s wealthiest cities and once known as the “city of gardens,” has been struggling to regulate air pollution. It is now considered one of the world’s most polluted cities.
Dangerous levels of air contamination have forced many of Lahore’s residents to stay at home, with some residents taking to social media, tweeting, “Lahore you’re killing me.”
Mohydin said air quality severely declined to unsafe levels in November, with one out of every two days since the beginning of the month having been classified as “hazardous'” by air quality monitors implemented by the Pakistan Air Quality Initiative and the city’s US Consulate. She said residents have not had healthy air for a single day in 2019.
Mohydin explained that the “smog season” in the eastern province typically runs from October to February when poor fuel quality, uncontrolled emissions and crop burning further deteriorate already unhealthy air.
Blame Pinned on India
Naseem-Ur-Rahman Shah, head of the provincial Environment Protection Department in Punjab, said thousands of people were treated this week at hospitals and clinics for respiratory-related diseases including asthma, fever, flu and cough.
While Shah warned people not to expose themselves to the harmful smog and said the government was “taking steps to control air pollution in Punjab,” Lahore residents still blamed the government’s inadequate measures to control air pollution.
“I don’t expect any action from the government to control toxic air,” 56-year-old Uzma Tareen, a local resident, told The Associated Press news agency.
Pakistan’s minister for the environment drew criticism last week after denying in a statement that the air quality in Lahore was hazardous.
Pakistan often blames poor air quality on farmers in India for burning waste in open fields.
“The fast blowing winds brought thick smog from India to Lahore and the international community should pressure India to take
measures for controlling air pollution as it also affects us,” said Shah.
Alex Jones Confronts Leftist Demons & Trump In Austin
During President Trump’s visit to Austin, Texas, Alex Jones shows up to confront him and is met by leftist demons against free speech.
By the way, overhaul your body’s cellular engine with our fan-favorite DNA Force Plus!


Jeremy Vine issues apology over huge cannabis blunder live on air
Vine told Billy McVie, 93, that he had "plenty of puff" to spare if the musician happened to run out during his time on the show
by James Rodger, https://www.facebook.com/jamesrodgerjournalistJeremy Vine has apologised after appearing to offer Scotland's oldest bagpipe player a "shedload" of cannabis.
The presenter, 54, made the gaffe on BBC Radio 2 during a live broadcast from Glasgow on Monday.
Vine told Billy McVie, 93, that he had "plenty of puff" to spare if the musician happened to run out during his time on the show.
Vine later apologised after being made aware that his comments could be interpreted as meaning "I've got a shedload of ganja".
He said on Twitter: "I apologise for the phrase I used earlier on the radio.
"While interviewing Scotland's oldest bagpiper, Billy McVie, 93, I told him: "I have got plenty of puff if you run out.
"I now understand that means 'I've got a shedload of ganja if you've smoked all yours'."
Mr McVie gave Vine a tutorial in playing the great Highland bagpipe, as well as a lesson in the instrument's history.
Referring to his guest as Bob, Vine told listeners: "Bob is on a mission to convince us that the bagpipe is capable of producing the most melodic and beautiful music and that it has unfairly been described as discordant and screechy.
"The joy of having you here is that we can cleanse our minds of all the election talk now.
"We don't have to do any politics. Do we? You don't need to say anything about politics here."
Earlier in the programme, a General Election special, Vine discussed Glasgow's "international reputation" for "the scourge of drugs" and spoke to a former heroin addict helping others in the city to fight addiction.


:ref:emphasis :ref:boldface :ref:some code sample
This is a bulleted list
item uses two lines
parent
parent
- child
- child
parent
Definition of the term, which must be indented
and can even consist of multiple paragraphs
This is a normal text paragraph. The next paragraph is a code sample:
It is not processed in any way, except
that the indentation is removed.
It can span multiple lines.
This is a normal text paragraph again.
| Header row, column 1 (header rows optional) | Header 2 | Header 3 | Header 4 |
|---|---|---|---|
| body row 1, column 1 | column 2 | column 3 | column 4 |
| body row 2 | ... | ... |
| A | B | A and B |
|---|---|---|
| False | False | False |
| True | False | False |
| False | True | False |
| True | True | True |
Go to Google google_link.


UCAN
Search
Chat
Bookmarks
My Profile
Hello user {{id}}! Welcome to UCAN!
Topics you're following:
Topic Name
Followers
{{topic.name}}
{{topic.followerCount}}
Uh oh!
We noticed you haven't chosen any topics yet!
Choose some topics to populate your feed.
Choose Topics


Pedestrian trust in automated vehicles in virtual reality
Pedestrians’ acceptance of automated vehicles (AVs) depends on their trust in the AVs, which in turn depends on the communication between pedestrians and the AV. AVs can communicate their intent through explicit or implicit means. Traditional methods of explicit communication in human-driven vehicles (HDVs) include indicator lamps, brake lamps, and horns. Implicit rather than explicit communication is a less explored approach to tackling the communication challenge and promoting trust between pedestrians and AVs. Implicit vehicle communication refers to the behavior cues derived from the vehicle’s driving. Similarly, the pedestrians can implicitly commmunicate through their motion, gesture, gaze, etc.
We developed a model of pedestrians’ trust in AVs based on AV driving behavior and traffic signal presence. To empirically verify this model, we conducted a human–subject study with 30 participants in a virtual reality environment. The study manipulated two factors: AV driving behavior (defensive, normal, and aggressive) and the crosswalk type (signalized and unsignalized crossing). Results indicate that pedestrians’ trust in AVs was influenced by AV driving behavior as well as the presence of a signal light. In addition, the impact of the AV’s driving behavior on trust in the AV depended on the presence of a signal light. There were also strong correlations between trust in AVs and certain observable trusting behaviors such as pedestrian gaze at certain areas/objects, pedestrian distance to collision, and pedestrian jaywalking time. We also present implications for design and future research.


Every Freshman Advisory is paired with two Link Crew members (one Senior and one Junior). The Link Crew members visit their freshman advisories once a month to play games, answer questions, and just generally be awesome! We have found that this process helps break the ice between advisory members and helps the freshman acclimate to high school life. Contact us if you have any questions or want to find out how to become a Link Crew member!
MembersSend us a message any time, we'll be happy to respond! (Even if it's 3 in the morning, trust us)
We're like instant noodles. You will have 2 friends the second you step on campus during Freshman Orientation!
We'll help you navigate through the Upper School! (Not sponsored by Google, but we're open to the idea)
Yes, it is cheesy, but we really do love our Link Buddies! There is nothing else to it!
Have questions? Send us an email or a fax! Actually, don't fax us because none of us know how to work a fax machine...
Seriously, don't fax us


We are a reference point at the national level, leaders in the educational community, recognized for the high quality of our services, acting with social sensitivity, and committed to a culture of excellence and success in life.
Enrollment is open year-around. Call, email or visit the school office for more information.
Full and partial scholarships for academic and artistic excellence are available to students who have been enrolled in the school for at least one year.
Hughes Schools is a bilingual educational institution whose mission it is to train and educate students of integrity and accomplishment, using the tools of academic and artistic excellence in an atmosphere of safety and security. We have a committed team of specialized professionals who are continuously researching and updating teaching methods appropriate for the constantly changing educational environment in order to respond to the needs of students, society, and the nation. We maintain excellent communication with our students and all sectors of the global community based on respect and mutual understanding.
The Hughes Schools Academic Program is organized on a daily schedule of six 45-minute classes, leading to a high school diploma and university success.
Hughes Schools students have been awarded more than 160 individual distinctions for Academic Excellence, including the following:
Sponsored by the United States Department of State and the National Youth Science Foundation, this scholarship is awarded to academically talented students to develop their highest potential in the sciences. The month-long program takes place in the state of West Virginia and the scholarship includes all travel and living expenses.
Students receive a full scholarship to attend the United Space School in Houston, Texas. Scholarship winners participate in a variety of space-related activities at the Johnson Space Center, the University of Houston Clear Lake, and Space Center Houston. Activities promote science, technology, engineering and mathematics (STEM) studies and international collaborations.
C-Tech2 is held on the campus of Virginia Tech University in Blacksburg, Virginia. Students participate in a wide-variety of engineering activities and projects and attend informational sessions on topics such as college admissions and scholarships, career planning and the engineering majors.
Over 100 Hughes Schools students have received Gold and Silver medals in a wide range of theoretical exam competitions sponsored by the Universidad Mayor de San Simon and the Government of Bolivia.
Leading to a high school diploma in the Performing Arts and future study in a conservatory program in dance or music.
Over 200 national and international Hughes Schools performances include:
Recent participation has included the Sestu International Folk Festival in Sestu, Italy, the Friendship Folk Festival in Iquique, Chile, and the Magic Valley Folk Festival, World Folkfest, and Summerfest Folk Festival in the states of Utah and Idaho, in the United States (July and August 2016).
Recent Hughes Schools fully-staged dance and musical productions include Happy Feet, Mary Poppins, and The Wizard of Oz.
Past, award winning participation has included the Bolivian National Choir contest finals in Santa Cruz, Bolivia, and in Cobija, Bolivia, and the Ibero-americano Choir Festival in Sucre, Bolivia.
The Hughes Schools graduate is
an ordinary person who does
extraordinary things.
He or she is a leader who in thought, voice, and action applies positive values and personal knowledge for self-growth and to improve the world.
With solid logical, critical, and creative thinking, the Hughes Schools graduate sets high goals and reaches them with excellence.
Thoughtful, active, and productive, he or she has the tools to achieve anything at any time and uses these abilities to the great social benefit of family, friends, community, and country.
Richard Hughes
Co-Principal
Dalcy Hughes
Co-Principal
Alvaro Lanza
Vice-Principal
What our students say