django.conf.urls utility functionsLink para este cabeçalho#static()Link para este cabeçalho#Helper function to return a URL pattern for serving files in debug mode:
\nfrom django.conf import settings\nfrom django.conf.urls.static import static\n\nurlpatterns = [\n # ... the rest of your URLconf goes here ...\n] + static(settings.MEDIA_URL, document_root=settings.MEDIA_ROOT)\nurl()Link para este cabeçalho#urlpatterns should be a list of url() instances. For example:
from django.conf.urls import include, url\n\nurlpatterns = [\n url(r'^index/$', index_view, name='main-view'),\n url(r'^weblog/', include('blog.urls')),\n ...\n]\nThe regex parameter should be a string or\nugettext_lazy() (see\nTranslating URL patterns) that contains a regular expression compatible\nwith Python’s re module. Strings typically use raw string syntax\n(r'') so that they can contain sequences like \\d without the need to\nescape the backslash with another backslash.
The view parameter is a view function or the result of\nas_view() for class-based views. It can\nalso be an include().
The kwargs parameter allows you to pass additional arguments to the view\nfunction or method. See Passando opções extras para função “view” for an example.
See Naming URL patterns for why the name\nparameter is useful.
include()Link para este cabeçalho#A function that takes a full Python import path to another URLconf module\nthat should be “included” in this place. Optionally, the application\nnamespace and instance namespace where the entries will be included\ninto can also be specified.
\nUsually, the application namespace should be specified by the included\nmodule. If an application namespace is set, the namespace argument\ncan be used to set a different instance namespace.
include() also accepts as an argument either an iterable that returns\nURL patterns, a 2-tuple containing such iterable plus the names of the\napplication namespaces, or a 3-tuple containing the iterable and the names\nof both the application and instance namespace.
module – URLconf module (or module name)
namespace (str) – Instance namespace for the URL entries being included
app_name (str) – Application namespace for the URL entries being included
pattern_list – Iterable of django.conf.urls.url() instances
app_namespace (str) – Application namespace for the URL entries being included
instance_namespace (str) – Instance namespace for the URL entries being included
See Incluindo outros URLconfs and Domínios de nomes de URL e URLconfs incluídos.
\n\nhandler400Link para este cabeçalho#A callable, or a string representing the full Python import path to the view\nthat should be called if the HTTP client has sent a request that caused an error\ncondition and a response with a status code of 400.
\nBy default, this is 'django.views.defaults.bad_request'. If you\nimplement a custom view, be sure it returns an\nHttpResponseBadRequest.
See the documentation about the 400 (bad request) view for more information.
\nhandler403Link para este cabeçalho#A callable, or a string representing the full Python import path to the view\nthat should be called if the user doesn’t have the permissions required to\naccess a resource.
\nBy default, this is 'django.views.defaults.permission_denied'. If you\nimplement a custom view, be sure it returns an\nHttpResponseForbidden.
See the documentation about the 403 (HTTP Forbidden) view for more information.
\nhandler404Link para este cabeçalho#A callable, or a string representing the full Python import path to the view\nthat should be called if none of the URL patterns match.
\nBy default, this is 'django.views.defaults.page_not_found'. If you\nimplement a custom view, be sure it returns an\nHttpResponseNotFound.
See the documentation about the 404 (HTTP Not Found) view for more information.
\nhandler500Link para este cabeçalho#A callable, or a string representing the full Python import path to the view\nthat should be called in case of server errors. Server errors happen when you\nhave runtime errors in view code.
\nBy default, this is 'django.views.defaults.server_error'. If you\nimplement a custom view, be sure it returns an\nHttpResponseServerError.
See the documentation about the 500 (HTTP Internal Server Error) view for more information.
\n