Django 1.6.6 开发指南：快速入门与核心功能详解

需积分: 10 108 浏览量更新于2024-07-22 收藏 4.89MB PDF 举报

Django开发文档是一份详细的指南，由Django Software Foundation提供，主要针对Python编程语言构建的高级Web应用程序框架。该文档适用于初学者和经验丰富的开发者，涵盖了从入门到高级主题的广泛内容。 1.1 获取帮助：文档首先介绍了如何获取帮助，包括官方社区、邮件列表、论坛和在线文档，以确保开发者在遇到问题时能够及时找到解决方案。 1.2 首步学习：章节1.2引导读者快速上手，通过简明扼要的步骤指导如何安装Django和理解其基本概念，如项目结构和工作流程。 1.3 Model层：这部分阐述了Django的数据模型系统，讲解如何定义数据结构（模型），以及如何与数据库进行交互，包括模型字段、表单验证和关系管理。 1.4 View层：这是文档的核心部分，介绍视图函数（views）的作用，如何处理HTTP请求并将数据传递给模板，实现前端与后端逻辑的连接。 1.5 Template层：这部分详细介绍了Django的模板语言，如何创建动态HTML页面，以及如何嵌套、继承和利用模板标签进行数据绑定和条件渲染。 1.6 表单：Django提供了强大的表单处理能力，这部分涵盖了如何创建和使用内置表单类，以及自定义表单组件。 1.7 开发过程：文档还涉及开发过程中的最佳实践，如版本控制、测试和部署策略，以确保项目的高效和可靠性。 1.8 Admin界面：Django的内置管理站点被详细解释，它如何帮助开发者轻松管理数据和模型实例，以及如何扩展自定义功能。 1.9 安全性：文档强调了Django的安全特性，如认证、授权、会话管理和跨站请求伪造防护等，保证应用程序的用户数据安全。 1.10 国际化和本地化：Django支持多语言应用，这里介绍了如何处理语言切换、日期时间格式和文化差异等问题。 1.11 Python兼容性：文档确保读者了解Django与不同Python版本的兼容性，以及可能遇到的问题和解决方案。 1.12 地理框架：如果项目需要地理位置相关功能，这部分会介绍如何集成和使用Django的地理工具。 1.13 其他核心功能：包括缓存、邮件系统、静态文件管理和静态类型检查等，这些都是Django框架的重要组成部分。 1.14 Django开源项目：文档概述了Django作为一个活跃的开源项目，其贡献者社区、许可证和持续更新的重要性。 2.1-2.11 部分主要介绍了“Getting started”（入门教程），逐步引导读者编写第一个Django应用，分为多个部分，涵盖了从设置环境到实现完整功能的全过程。 2.11 进阶：如何为Django写第一个补丁，让开发者了解参与开源项目的贡献方式。 3.1 和3.2 分别介绍了Django的安装方法和模型与数据库的深入使用，确保开发者能稳定地搭建和管理他们的项目。 Django开发文档是开发人员不可或缺的参考资料，它全面而详尽地涵盖了Django框架的基础知识和关键概念，帮助开发者构建高质量的Web应用。

Django Documentation, Release 1.6.6.dev20140722172802

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.

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 Python 2.6, 2.7, 3.2 or 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:

10 Chapter 2. Getting started

Django Documentation, Release 1.6.6.dev20140722172802

• 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.

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.6

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.6 and Python 2.x. If the Django version doesn’t match, you can refer to the tutorial

for your version of Django by using the version switcher at the bottom right corner of this page, 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.

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

Django Documentation, Release 1.6.6.dev20140722172802

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.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/ root 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.

12 Chapter 2. Getting started

Django Documentation, Release 1.6.6.dev20140722172802

• 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. mysite.urls).

• 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.)

• mysite/settings.py: Settings/conﬁguration for this Django project. Django settings will tell you all

about how settings work.

• mysite/urls.py: The URL declarations for this Django project; a “table of contents” of your Django-

powered site. You can read more about URLs in URL dispatcher.

• mysite/wsgi.py: An entry-point for WSGI-compatible web servers to serve your project. See How to

deploy with WSGI for more details.

The development server

Let’s verify this worked. Change into the outer mysite directory, if you haven’t already, and run the command

python manage.py runserver. You’ll see the following output on the command line:

Validating models...

0 errors found

July 22, 2014 - 15:50:53

Django version 1.6, using settings ‘mysite.settings’

Starting development server at http://127.0.0.1:8000/

Quit the server with CONTROL-C.

You’ve started the Django development server, a lightweight Web server written purely in Python. We’ve included this

with Django so you can develop things rapidly, without having to deal with conﬁguring a production server – such as

Apache – until you’re ready for production.

Now’s a good time to note: Don’t use this server in anything resembling a production environment. It’s intended only

for use while developing. (We’re in the business of making Web frameworks, not Web servers.)

Now that the server’s running, visit http://127.0.0.1:8000/ with your Web browser. You’ll see a “Welcome to Django”

page, in pleasant, light-blue pastel. It worked!

Changing the port

By default, the runserver command starts the development server on the internal IP at port 8000.

If you want to change the server’s port, pass it as a command-line argument. For instance, this command starts the

server on port 8080:

$ python manage.py runserver 8080

If you want to change the server’s IP, pass it along with the port. So to listen on all public IPs (useful if you want to

show off your work on other computers), use:

$ python manage.py runserver 0.0.0.0:8000

Full docs for the development server can be found in the runserver reference.

Automatic reloading of runserver

The development server automatically reloads Python code for each request as needed. You don’t need to restart the

server for code changes to take effect. However, some actions like adding ﬁles or compiling translation ﬁles don’t

trigger a restart, so you’ll have to restart the server in these cases.

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

Django Documentation, Release 1.6.6.dev20140722172802

Database setup

Now, edit mysite/settings.py. It’s a normal Python module with module-level variables representing Django

settings.

By default, the conﬁguration uses SQLite. If you’re new to databases, or you’re just interested in trying Django, this is

the easiest choice. SQLite is included in Python, so you won’t need to install anything else to support your database.

If you wish to use another database, install the appropriate database bindings, and change the following keys in the

DATABASES ’default’ item to match your database connection settings:

• ENGINE – Either ’django.db.backends.sqlite3’, ’django.db.backends.postgresql_psycopg2’,

’django.db.backends.mysql’, or ’django.db.backends.oracle’. Other backends are also

available.

• NAME – The name of your database. If you’re using SQLite, the database will be a ﬁle on your computer;

in that case, NAME should be the full absolute path, including ﬁlename, of that ﬁle. The default value,

os.path.join(BASE_DIR, ’db.sqlite3’), will store the ﬁle in your project directory.

If you are not using SQLite as your database, additional settings such as USER, PASSWORD, HOST must be added.

For more details, see the reference documentation for DATABASES.

Note: If you’re using PostgreSQL or MySQL, make sure you’ve created a database by this point. Do that with

“CREATE DATABASE database_name;” within your database’s interactive prompt.

If you’re using SQLite, you don’t need to create anything beforehand - the database ﬁle will be created automatically

when it is needed.

While you’re editing mysite/settings.py, set TIME_ZONE to your time zone.

Also, note the INSTALLED_APPS setting at the top of the ﬁle. That holds the names of all Django applications that

are activated in this Django instance. Apps can be used in multiple projects, and you can package and distribute them

for use by others in their projects.

By default, INSTALLED_APPS contains the following apps, all of which come with Django:

• django.contrib.admin – The admin site. You’ll use it in part 2 of this tutorial.

• django.contrib.auth – An authentication system.

• django.contrib.contenttypes – A framework for content types.

• django.contrib.sessions – A session framework.

• django.contrib.messages – A messaging framework.

• django.contrib.staticfiles – A framework for managing static ﬁles.

These applications are included by default as a convenience for the common case.

Some of these applications makes use of at least one database table, though, so we need to create the tables in the

database before we can use them. To do that, run the following command:

$ python manage.py syncdb

The syncdb command looks at the INSTALLED_APPS setting and creates any necessary database tables according

to the database settings in your mysite/settings.py ﬁle. You’ll see a message for each database table it creates,

and you’ll get a prompt asking you if you’d like to create a superuser account for the authentication system. Go ahead

and do that.

If you’re interested, run the command-line client for your database and type \dt (PostgreSQL), SHOW TABLES;

(MySQL), or .schema (SQLite) to display the tables Django created.

14 Chapter 2. Getting started

剩余1375页未读，继续阅读

u010380540

粉丝: 0
资源: 3

Django 1.6.6 开发指南：快速入门与核心功能详解

django中文官方文档

django 文档

Django 2.0.6 开发文档

django4.0中文文档

django项目的开发文档？

django开发难度如何

pycharm django 商城源码

django开发从入门到实践+python django web典型模块开发实战

django+vue3 全栈开发学习文档

你为什么选择Django开发项目

最新资源