org/z/6PdebYn1K) (*) 5. https://fmt.dev/latest/api.html#formatting-user-defined-types7 Slides1. Namespaces ordering: https://godbolt.org/z/qvMcYn1Kd (if in both the namespace and the argument’s namespace) redeclarations are only allowed • after the point of declaration, • at namespace scope, and • in namespaces that enclose the original namespace (including the global namespace). Also, they must use qualified-id Improvement of usage: https://godbolt.org/z/qnnEbf3qo @@@ Now we can move implementations across namespaces, in a non-intrusive way1 Slides@@@ All templates can be constrained with concepts1 Slides1. @@@

include('django.contrib.staticfiles.urls')), ) + urlpatterns Change your url and reverse calls to language namespaces. We now support the django way of calling other language urls either via {% language %} templatetag TEMPLATE_CONTEXT_PROCESSORS setting. All templates in CMS_TEMPLATES must at least contain the js and css sekizai namespaces. Please refer to the documentation on Handling media in custom CMS plugins and the django-sekizai django-sekizai [https://github.com/ojii/django-sekizai]. This requires you to define at least two sekizai namespaces in your templates: js and css. You can do so using the render_block template tag from the sekizai_tags

include('django.contrib.staticfiles.urls')), ) + urlpatterns • Change your url and reverse calls to language namespaces. We now support the django way of calling other language urls either via {% language %} templatetag TEMPLATE_CONTEXT_PROCESSORS setting. All templates in CMS_TEMPLATES must at least contain the js and css sekizai namespaces. Please refer to the documentation on Handling media in custom CMS plugins and the django-sekizai required by CMS plugins using django- sekizai. This requires you to define at least two sekizai namespaces in your templates: js and css. You can do so using the render_block template tag from the sekizai_tags

required by CMS plugins using django-sekizai. This requires you to define at least two sekizai namespaces in your templates: js and css. You can do so using the render_block template tag from the sekizai_tags your namespace will change. The solution for this problem are application namespaces. If you’d like to use application namespaces to reverse the URLs related to your app, you can assign a value to the app_name application and instance namespaces, the current_app scope and the reversing of such URLs. You can look it up at https://docs.djangoproject.com/en/dev/topics/http/urls/#url-namespaces When using the reverse

com/ojii/django- sekizai]. Your CMS templates are always enforced to have the css and js sekizai namespaces, therefore those should be used to include the respective files. For more information about django-sekizai namespaced URLs [https://docs.djangoproject.com/en/2.2/topics/http/urls/#topics-http-defining-url-namespaces]. In the example above, the application uses the myapp namespace. Your CMSApp sub- class must reflect app_name if a match is found. This arrangement allows you to use multiple application instances and namespaces if that flexibility is required, while guaranteeing a simple way to make it work when it’s not

com/ojii/django- sekizai]. Your CMS templates are always enforced to have the css and js sekizai namespaces, therefore those should be used to include the respective files. For more information about django-sekizai namespaced URLs [https://docs.djangoproject.com/en/2.2/topics/http/urls/#topics-http-defining-url-namespaces]. In the example above, the application uses the myapp namespace. Your CMSApp sub- class must reflect app_name if a match is found. This arrangement allows you to use multiple application instances and namespaces if that flexibility is required, while guaranteeing a simple way to make it work when it’s not

template using django-sekizai. Your CMS templates are always enforced to have the css and js sekizai namespaces, therefore those should be used to include the respective files. For more information about django-sekizai app_name if a match is found. This arrangement allows you to use multiple application instances and namespaces if that flexibility is required, while guaranteeing a simple way to make it work when it’s not apphook (don’t forget to publish them), with different namespaces and different config- urations. Also create some entries assigned to the two namespaces. You can experiment with the different configured behaviours

template using django-sekizai. Your CMS templates are always enforced to have the css and js sekizai namespaces, therefore those should be used to include the respective files. For more information about django-sekizai app_name if a match is found. This arrangement allows you to use multiple application instances and namespaces if that flexibility is required, while guaranteeing a simple way to make it work when it’s not apphook (don’t forget to publish them), with different namespaces and different config- urations. Also create some entries assigned to the two namespaces. You can experiment with the different configured behaviours

com/ojii/django- sekizai]. Your CMS templates are always enforced to have the css and js sekizai namespaces, therefore those should be used to include the respective files. For more information about django-sekizai namespaced URLs [https://docs.djangoproject.com/en/4.2/topics/http/urls/#topics-http-defining-url-namespaces]. In the example above, the application uses the myapp namespace. Your CMSApp sub- class must reflect app_name if a match is found. This arrangement allows you to use multiple application instances and namespaces if that flexibility is required, while guaranteeing a simple way to make it work when it’s not

com/ojii/django- sekizai]. Your CMS templates are always enforced to have the css and js sekizai namespaces, therefore those should be used to include the respective files. For more information about django-sekizai namespaced URLs [https://docs.djangoproject.com/en/4.2/topics/http/urls/#topics-http-defining-url-namespaces]. In the example above, the application uses the myapp namespace. Your CMSApp sub- class must reflect app_name if a match is found. This arrangement allows you to use multiple application instances and namespaces if that flexibility is required, while guaranteeing a simple way to make it work when it’s not