Django 1.5.1 官方文档指南

需积分: 10 54 浏览量更新于2024-07-20 收藏 7.06MB PDF 举报

"Django 1.5.1 官方文档" Django 是一个基于 Python 语言的自由开源的 web 应用框架，由 Adrian Holovaty 和 Simon Willison 于 2003 年创立。Django 的主要目标是帮助开发者快速构建可维护、可扩展的网站。Django 的设计哲学是基于模型-视图-模板（MVC）架构，提供了一个强大且灵活的框架来构建 web 应用程序。根据官方文档，Django 1.5.1 的主要特点包括： 1. 模型层（Model Layer）：Django 的模型层是基于数据库的抽象，提供了一个统一的接口来访问数据库。模型层定义了数据模型，并提供了一个简洁的方式来访问和操作数据。 2. 视图层（View Layer）：Django 的视图层是负责处理 HTTP 请求和响应的层，提供了一个灵活的方式来处理用户请求。视图层可以使用函数或类来定义视图函数，并提供了一个简洁的方式来处理请求和响应。 3. 模板层（Template Layer）：Django 的模板层是负责渲染 HTML 模板的层，提供了一个灵活的方式来渲染模板。模板层使用 Jinja2 模板引擎，提供了一个强大且灵活的方式来渲染模板。 4. 表单（Forms）：Django 的表单系统提供了一个简洁的方式来处理用户输入，提供了一个灵活的方式来验证用户输入。 5. 开发过程（The Development Process）：Django 的开发过程提供了一个简洁的方式来开发和测试应用程序，提供了一个灵活的方式来 debug 和优化应用程序。 6. 安全性（Security）：Django 的安全性系统提供了一个简洁的方式来保护应用程序免受攻击，提供了一个灵活的方式来处理身份验证和授权。 7. 国际化和本地化（Internationalization and Localization）：Django 的国际化和本地化系统提供了一个简洁的方式来处理多语言支持，提供了一个灵活的方式来支持不同语言和地区。 8. Python 兼容性（Python Compatibility）：Django 的 Python 兼容性系统提供了一个简洁的方式来支持不同版本的 Python，提供了一个灵活的方式来支持 Python 2.x 和 Python 3.x。 9. 地理信息框架（Geographic Framework）：Django 的地理信息框架提供了一个简洁的方式来处理地理信息，提供了一个灵活的方式来支持地理信息应用程序。 10. 通用 Web 应用程序工具（Common Web Application Tools）：Django 的通用 Web 应用程序工具提供了一个简洁的方式来支持常见的 Web 应用程序任务，提供了一个灵活的方式来开发和维护 Web 应用程序。 11. Django 开源项目（The Django Open-Source Project）：Django 的开源项目提供了一个简洁的方式来参与 Django 的开发和维护，提供了一个灵活的方式来贡献代码和反馈。 Django 1.5.1 的官方文档提供了一个详细的指南来学习和使用 Django，涵盖了从基础知识到高级主题的所有方面。

Django Documentation, Release 1.5.1

To design URLs for an app, you create a Python module called a URLconf . A table of contents for your app, it contains

a simple mapping between URL patterns and Python callback functions. URLconfs also serve to decouple URLs from

Python code.

Here’s what a URLconf might look like for the Reporter/Article example above:

from django.conf.urls import patterns

urlpatterns = patterns(’’,

(r’^articles/(\d{4})/$’, ’news.views.year_archive’),

(r’^articles/(\d{4})/(\d{2})/$’, ’news.views.month_archive’),

(r’^articles/(\d{4})/(\d{2})/(\d+)/$’, ’news.views.article_detail’),

)

The code above maps URLs, as simple regular expressions, to the location of Python callback functions (“views”).

The regular expressions use parenthesis to “capture” values from the URLs. When a user requests a page, Django runs

through each pattern, in order, and stops at the ﬁrst one that matches the requested URL. (If none of them matches,

Django calls a special-case 404 view.) This is blazingly fast, because the regular expressions are compiled at load

time.

Once one of the regexes matches, Django imports and calls the given view, which is a simple Python function. Each

view gets passed a request object – which contains request metadata – and the values captured in the regex.

For example, if a user requested the URL “/articles/2005/05/39323/”, Django would call the function

news.views.article_detail(request, ’2005’, ’05’, ’39323’).

2.1.6 Write your views

Each view is responsible for doing one of two things: Returning an HttpResponse object containing the content

for the requested page, or raising an exception such as Http404. The rest is up to you.

Generally, a view retrieves data according to the parameters, loads a template and renders the template with the

retrieved data. Here’s an example view for year_archive from above:

def year_archive(request, year):

a_list = Article.objects.filter(pub_date__year=year)

return render_to_response(’news/year_archive.html’, {’year’: year, ’article_list’: a_list})

This example uses Django’s template system, which has several powerful features but strives to stay simple enough

for non-programmers to use.

2.1.7 Design your templates

The code above loads the news/year_archive.html template.

Django has a template search path, which allows you to minimize redundancy among templates. In your Django

settings, you specify a list of directories to check for templates. If a template doesn’t exist in the ﬁrst directory, it

checks the second, and so on.

Let’s say the news/year_archive.html template was found. Here’s what that might look like:

{% extends "base.html" %}

{% block title %}Articles for {{ year }}{% endblock %}

{% block content %}

<h1>Articles for {{ year }}</h1>

10 Chapter 2. Getting started

Django Documentation, Release 1.5.1

{% for article in article_list %}

<p>{{ article.headline }}</p>

<p>By {{ article.reporter.full_name }}</p>

<p>Published {{ article.pub_date|date:"F j, Y" }}</p>

{% endfor %}

{% endblock %}

Variables are surrounded by double-curly braces. {{ article.headline }} means “Output the value of the

article’s headline attribute.” But dots aren’t used only for attribute lookup: They also can do dictionary-key lookup,

index lookup and function calls.

Note {{ article.pub_date|date:"F j, Y" }} uses a Unix-style “pipe” (the “|” character). This is called

a template ﬁlter, and it’s a way to ﬁlter the value of a variable. In this case, the date ﬁlter formats a Python datetime

object in the given format (as found in PHP’s date function).

You can chain together as many ﬁlters as you’d like. You can write custom ﬁlters. You can write custom template tags,

which run custom Python code behind the scenes.

Finally, Django uses the concept of “template inheritance”: That’s what the {% extends "base.html" %}

does. It means “First load the template called ‘base’, which has deﬁned a bunch of blocks, and ﬁll the blocks with

the following blocks.” In short, that lets you dramatically cut down on redundancy in templates: each template has to

deﬁne only what’s unique to that template.

Here’s what the “base.html” template, including the use of static ﬁles, might look like:

{% load staticfiles %}

<html>

<head>

<title>{% block title %}{% endblock %}</title>

</head>

<body>

{% block content %}{% endblock %}

</body>

</html>

Simplistically, it deﬁnes the look-and-feel of the site (with the site’s logo), and provides “holes” for child templates to

ﬁll. This makes a site redesign as easy as changing a single ﬁle – the base template.

It also lets you create multiple versions of a site, with different base templates, while reusing child templates. Django’s

creators have used this technique to create strikingly different cell-phone editions of sites – simply by creating a new

base template.

Note that you don’t have to use Django’s template system if you prefer another system. While Django’s template

system is particularly well-integrated with Django’s model layer, nothing forces you to use it. For that matter, you

don’t have to use Django’s database API, either. You can use another database abstraction layer, you can read XML

ﬁles, you can read ﬁles off disk, or anything you want. Each piece of Django – models, views, templates – is decoupled

from the next.

2.1.8 This is just the surface

This has been only a quick overview of Django’s functionality. Some more useful features:

• A caching framework that integrates with memcached or other backends.

• A syndication framework that makes creating RSS and Atom feeds as easy as writing a small Python class.

• More sexy automatically-generated admin features – this overview barely scratched the surface.

2.1. Django at a glance 11

Django Documentation, Release 1.5.1

The next obvious steps are for you to download Django, read the tutorial and join the community. Thanks for your

interest!

2.2 Quick install guide

Before you can use Django, you’ll need to get it installed. We have a complete installation guide that covers all

the possibilities; this guide will guide you to a simple, minimal installation that’ll work while you walk through the

introduction.

2.2.1 Install Python

Being a Python Web framework, Django requires Python. It works with any Python version from 2.6.5 to 2.7. It also

features experimental support for versions 3.2 and 3.3. All these versions of Python include a lightweight database

called SQLite so you won’t need to set up a database just yet.

Get Python at http://www.python.org. If you’re running Linux or Mac OS X, you probably already have it installed.

Django on Jython

If you use Jython (a Python implementation for the Java platform), you’ll need to follow a few additional steps. See

Running Django on Jython for details.

You can verify that Python is installed by typing python from your shell; you should see something like:

Python 2.6.6 (r266:84292, Dec 26 2010, 22:31:48)

[GCC 4.4.5] on linux2

Type "help", "copyright", "credits" or "license" for more information.

>>>

2.2.2 Set up a database

This step is only necessary if you’d like to work with a “large” database engine like PostgreSQL, MySQL, or Oracle.

To install such a database, consult the database installation information.

2.2.3 Remove any old versions of Django

If you are upgrading your installation of Django from a previous version, you will need to uninstall the old Django

version before installing the new version.

2.2.4 Install Django

You’ve got three easy options to install Django:

• Install a version of Django provided by your operating system distribution. This is the quickest option for those

who have operating systems that distribute Django.

• Install an ofﬁcial release. This is the best approach for users who want a stable version number and aren’t

concerned about running a slightly older version of Django.

• Install the latest development version. This is best for users who want the latest-and-greatest features and aren’t

afraid of running brand-new code.

12 Chapter 2. Getting started

Django Documentation, Release 1.5.1

Always refer to the documentation that corresponds to the version of Django you’re using!

If you do either of the ﬁrst two steps, keep an eye out for parts of the documentation marked new in development

version. That phrase ﬂags features that are only available in development versions of Django, and they likely won’t

work with an ofﬁcial release.

2.2.5 Verifying

To verify that Django can be seen by Python, type python from your shell. Then at the Python prompt, try to import

Django:

>>> import django

>>> print(django.get_version())

1.5

You may have another version of Django installed.

2.2.6 That’s it!

That’s it – you can now move onto the tutorial.

2.3 Writing your ﬁrst Django app, part 1

Let’s learn by example.

Throughout this tutorial, we’ll walk you through the creation of a basic poll application.

It’ll consist of two parts:

• A public site that lets people view polls and vote in them.

• An admin site that lets you add, change and delete polls.

We’ll assume you have Django installed already. You can tell Django is installed and which version by running the

following command:

python -c "import django; print(django.get_version())"

If Django is installed, you should see the version of your installation. If it isn’t, you’ll get an error telling “No module

named django”.

This tutorial is written for Django 1.5 and Python 2.x. If the Django version doesn’t match, you can refer to the tutorial

for your version of Django or update Django to the newest version. If you are using Python 3.x, be aware that your

code may need to differ from what is in the tutorial and you should continue using the tutorial only if you know what

you are doing with Python 3.x.

See How to install Django for advice on how to remove older versions of Django and install a newer one.

Where to get help:

If you’re having trouble going through this tutorial, please post a message to django-users or drop by #django on

irc.freenode.net to chat with other Django users who might be able to help.

2.3. Writing your ﬁrst Django app, part 1 13

Django Documentation, Release 1.5.1

2.3.1 Creating a project

If this is your ﬁrst time using Django, you’ll have to take care of some initial setup. Namely, you’ll need to auto-

generate some code that establishes a Django project – a collection of settings for an instance of Django, including

database conﬁguration, Django-speciﬁc options and application-speciﬁc settings.

From the command line, cd into a directory where you’d like to store your code, then run the following command:

django-admin.py startproject mysite

This will create a mysite directory in your current directory. If it didn’t work, see Problems running django-

admin.py.

Note: You’ll need to avoid naming projects after built-in Python or Django components. In particular, this means

you should avoid using names like django (which will conﬂict with Django itself) or test (which conﬂicts with a

built-in Python package).

Where should this code live?

If your background is in plain old PHP (with no use of modern frameworks), you’re probably used to putting code

under the Web server’s document root (in a place such as /var/www). With Django, you don’t do that. It’s not a

good idea to put any of this Python code within your Web server’s document root, because it risks the possibility that

people may be able to view your code over the Web. That’s not good for security.

Put your code in some directory outside of the document root, such as /home/mycode.

Let’s look at what startproject created:

mysite/

manage.py

mysite/

__init__.py

settings.py

urls.py

wsgi.py

Doesn’t match what you see?

The default project layout recently changed. If you’re seeing a “ﬂat” layout (with no inner mysite/ directory),

you’re probably using a version of Django that doesn’t match this tutorial version. You’ll want to either switch to the

older tutorial or the newer Django version.

These ﬁles are:

• The outer mysite/ directory is just a container for your project. Its name doesn’t matter to Django; you can

rename it to anything you like.

• manage.py: A command-line utility that lets you interact with this Django project in various ways. You can

read all the details about manage.py in django-admin.py and manage.py.

• The inner mysite/ directory is the actual Python package for your project. Its name is the Python package

name you’ll need to use to import anything inside it (e.g. import mysite.settings).

• mysite/__init__.py: An empty ﬁle that tells Python that this directory should be considered a Python

package. (Read more about packages in the ofﬁcial Python docs if you’re a Python beginner.)

14 Chapter 2. Getting started

剩余1273页未读，继续阅读

若星汉灿烂

粉丝: 0
资源: 4

Django 1.5.1 官方文档指南

Python库 | django-kmuhelper-1.5.1.tar.gz

Python库 | manganelo-1.5.1-py3-none-any.whl

Python库 | django-pipeline-1.5.1.tar.gz

Django自带的django-cities和django-countries 示例

django-q2 与 django-celery

Django自带的django-cities和django-countries url配置示例

Django自带的django-cities和django-countries

django-admin startproject HelloWorld 'django-admin' 不是内部或外部命令，也不是可运行的程序 或批处理文件。

重新安裝djangorestframework后版本還是：Django==3.2.16 django-cors-headers==3.13.0 django-rest-framework==0.1.0 djangorestframework==3.14.0 djangorestframework-jwt==1.11.0

django-filter 1.1 需要配什么版本的django

最新资源

django-admin startproject HelloWorld 'django-admin' 不是内部或外部命令，也不是可运行的程序或批处理文件。