Django 1.4 官方文档详解：构建Web应用的必备指南

Django

官方文档

5星 · 超过95%的资源需积分: 9 179 浏览量更新于2024-07-25 2 收藏 6.38MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

"Django-1.4官方文档(pdf)提供了全面的Django框架技术指南，涵盖了从入门到进阶的各个层面，旨在帮助开发者熟练掌握Django的使用，包括模型层、模板层、视图层、表单处理、开发流程以及各种内置功能。文档由Django Software Foundation于2012年4月11日发布，是学习和参考Django 1.4版本的重要资源。" Django是一个流行的Python web框架，它遵循“DRY”（Don't Repeat Yourself）原则，提供了一套高效、简洁且可重用的组件，使得开发者能够快速构建高质量的Web应用。在Django 1.4官方文档中，我们可以找到以下关键知识点： 1. **获取帮助**：文档提供了多种获取Django社区支持和解决问题的途径，包括邮件列表、论坛、IRC频道等。 2. **第一步**：介绍如何开始使用Django，包括安装环境、设置项目和应用。 3. **模型层**：模型是Django中用于数据建模的类，描述数据库中的表结构。这里会讲解如何定义模型字段、关系以及模型管理器。 4. **模板层**：Django的模板系统允许开发者创建动态HTML页面。文档详细解释了模板语法、继承、过滤器和标签的使用。 5. **视图层**：视图是处理HTTP请求并返回响应的函数或类。文档中将介绍如何编写视图，以及如何处理GET和POST请求。 6. **表单**：Django提供了强大的表单处理能力，包括定义表单、验证用户输入、渲染表单及处理表单数据。 7. **开发过程**：涵盖了开发环境的配置、调试工具、版本控制和部署策略。 8. **其他内置功能**：包括中间件、缓存框架、用户认证和授权、静态文件处理、URL路由、国际化和本地化等。 9. **安装Django**：详述了在不同操作系统上的安装步骤，包括Python环境的设置和Django包的安装。 10. **模型与数据库**：讲解了如何通过模型操作数据库，包括查询、更新、删除记录，以及数据库迁移。 11. **处理HTTP请求**：介绍如何捕获和响应HTTP请求，包括视图函数的编写和请求对象的使用。 12. **工作与表单**：涵盖表单的创建、用户输入验证、表单数据的处理，以及如何在模板中渲染表单。 13. **Django模板语言**：详细阐述了模板语言的语法和特性，如变量、控制结构、过滤器和自定义标签。 14. **基于类的通用视图**：提供了一种更灵活的方式来创建视图，可以复用和组合。 15. **迁移函数式通用视图**：指导如何将传统的函数式视图转换为类基视图。 16. **文件管理**：涵盖了上传文件的处理、存储和访问。 17. **测试Django应用**：介绍了如何编写和运行单元测试、集成测试，确保代码质量。 18. **Django的用户认证框架**：详细讲解了用户注册、登录、权限和组的管理。 19. **缓存框架**：说明了如何利用Django的缓存机制提高网站性能。 20. **条件视图处理**：介绍了视图如何根据特定条件进行不同的处理。 21. **加密签名**：提供了用于安全存储和验证数据的方法。这份官方文档不仅是初学者的指南，也是有经验的Django开发者的重要参考资料，无论你是要构建一个新的项目还是优化现有应用，都能从中找到所需的帮助。

资源详情

资源推荐

Django Documentation, Release 1.4

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.5 to 2.7 (due to

backwards incompatibilities in Python 3.0, Django does not currently work with Python 3.0; see the Django FAQ for

more information on supported Python versions and the 3.0 transition), 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.5.1 (r251:54863, Jan 17 2008, 19:35:17)

[GCC 4.0.1 (Apple Inc. build 5465)] on darwin

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

>>>

2.2.2 Set up a database

If you installed Python 2.5 or later, you can skip this step for now.

If not, or if you’d like to work with a “large” database engine like PostgreSQL, MySQL, or Oracle, 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.

10 Chapter 2. Getting started

Django Documentation, Release 1.4

This will create a mysite directory in your current directory.

Script name may differ in distribution packages

If you installed Django using a Linux distribution’s package manager (e.g. apt-get or yum) django-admin.py

may have been renamed to django-admin. You may continue through this documentation by omitting .py from

each command.

Mac OS X permissions

If you’re using Mac OS X, you may see the message “permission denied” when you try to run django-admin.py

startproject. This is because, on Unix-based systems like OS X, a ﬁle must be marked as “executable” before it

can be run as a program. To do this, open Terminal.app and navigate (using the cd command) to the directory where

django-admin.py is installed, then run the command sudo chmod +x 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).

django-admin.py should be on your system path if you installed Django via python setup.py. If it’s not

on your path, you can ﬁnd it in site-packages/django/bin, where site-packages is a directory

within your Python installation. Consider symlinking to django-admin.py from some place on your path, such as

/usr/local/bin.

Where should this code live?

If your background is in PHP, 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.

12 Chapter 2. Getting started

Django Documentation, Release 1.4

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

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

Django version 1.4, using settings ’mysite.settings’

Development server is running 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.

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

Django Documentation, Release 1.4

Database setup

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

settings. Change the following keys in the DATABASES ’default’ item to match your database connection settings.

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

’django.db.backends.mysql’, ’django.db.backends.sqlite3’ 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. If the ﬁle doesn’t exist, it will

automatically be created when you synchronize the database for the ﬁrst time (see below).

When specifying the path, always use forward slashes, even on Windows (e.g.

C:/homes/user/mysite/sqlite3.db).

• USER – Your database username (not used for SQLite).

• PASSWORD – Your database password (not used for SQLite).

• HOST – The host your database is on. Leave this as an empty string if your database server is on the same

physical machine (not used for SQLite).

If you’re new to databases, we recommend simply using SQLite by setting ENGINE to

’django.db.backends.sqlite3’ and NAME to the place where you’d like to store the database. SQLite is

included as part of Python 2.5 and later, so you won’t need to install anything else to support your database.

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 settings.py, set TIME_ZONE to your time zone. The default value is the Central time zone

in the U.S. (Chicago).

Also, note the INSTALLED_APPS setting toward the bottom of the ﬁle. That holds the names of all Django appli-

cations 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.auth – An authentication system.

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

• django.contrib.sessions – A session framework.

• django.contrib.sites – A framework for managing multiple sites with one Django installation.

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

Each 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

14 Chapter 2. Getting started

剩余1171页未读，继续阅读

shou1989

粉丝: 0
资源: 4

Django 1.4 官方文档详解：构建Web应用的必备指南

Django-1.5.1 官方文档

django-widgy.pdf

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-rest-framework

django 使用django-crontab的详细案例

国内django-simpleui镜像

django-vue-admin

django-simple-menu

D:\code\python code>django-admin startproject bysms 'django-admin' 不是内部或外部命令，也不是可运行的程序 或批处理文件。

django安装后没有django-admin文件

django-admin 不是内部或外部命令

django-gridfs-storage

django-contrib-comments 和 django-comments-xtd 如何选择

D:\gyj>django-admin startproject mysite 'django-admin' 不是内部或外部命令，也不是可运行的程序

最新资源

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

D:\code\python code>django-admin startproject bysms 'django-admin' 不是内部或外部命令，也不是可运行的程序或批处理文件。