Asegúrese de que:
sys.path
(import mysite.settings
should work).El módulo no tiene errores de sintaxis (por supuesto).
Nosotros pensamos que nuestro motor de plantillas es la mejor cosa después de la tocineta en trozos, pero reconocemos que escoger un lenguaje de plantillas es cercano a la religión. No hay nada acerca de Django que requiera usar el lenguaje de plantillas, si estás apegado a Jinja2, Mako, o lo que sea, siéntete libre de usarlos.
Nope. Just like the template system, the model/database layer is decoupled from the rest of the framework.
The one exception is: If you use a different database library, you won’t get to use Django’s automatically-generated admin site. That app is coupled to the Django database layer.
Utilizar una:class:~django.db.models.FileField o una :class:`~django.db.models.ImageField`en un modelo toma unos pocos pasos:
MEDIA_ROOT
as
the full path to a directory where you’d like Django to store uploaded
files. (For performance, these files are not stored in the database.)
Define MEDIA_URL
as the base public URL of that directory.
Make sure that this directory is writable by the Web server’s user
account.FileField
or
ImageField
to your model, defining the
upload_to
option to specify a
subdirectory of MEDIA_ROOT
to use for uploaded files.MEDIA_ROOT
). You’ll most likely want to use the
convenience url
attribute
provided by Django. For example, if your
ImageField
is called mug_shot
, you can get
the absolute path to your image in a template with
{{ object.mug_shot.url }}
.Sometimes your templates just all need the same thing. A common example would be dynamically-generated menus. At first glance, it seems logical to simply add a common dictionary to the template context.
La solución correcta es usar un RequestContext
. Los detalles de cómo hacer esto están aquí: Subclassing Context: RequestContext.
ago. 01, 2016