Replaced http by https in djangoproject.com links
git-svn-id: http://code.djangoproject.com/svn/django/trunk@17703 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
69b96f824d
commit
78638a9a51
|
@ -401,7 +401,7 @@ TRANSACTIONS_MANAGED = False
|
|||
# The User-Agent string to use when checking for URL validity through the
|
||||
# isExistingURL validator.
|
||||
from django import get_version
|
||||
URL_VALIDATOR_USER_AGENT = "Django/%s (http://www.djangoproject.com)" % get_version()
|
||||
URL_VALIDATOR_USER_AGENT = "Django/%s (https://www.djangoproject.com)" % get_version()
|
||||
|
||||
# The tablespaces to use for each model when not specified otherwise.
|
||||
DEFAULT_TABLESPACE = ''
|
||||
|
|
|
@ -176,7 +176,7 @@ Technically, the docs on Django's site are generated from the latest development
|
|||
versions of those reST documents, so the docs on the Django site may offer more
|
||||
information than the docs that come with the latest Django release.
|
||||
|
||||
.. _stored in revision control: http://code.djangoproject.com/browser/django/trunk/docs
|
||||
.. _stored in revision control: https://code.djangoproject.com/browser/django/trunk/docs
|
||||
|
||||
Where can I find Django developers for hire?
|
||||
--------------------------------------------
|
||||
|
@ -188,4 +188,4 @@ You might also be interested in posting a job to http://djangogigs.com/ .
|
|||
If you want to find Django-capable people in your local area, try
|
||||
http://djangopeople.net/ .
|
||||
|
||||
.. _developers for hire page: http://code.djangoproject.com/wiki/DevelopersForHire
|
||||
.. _developers for hire page: https://code.djangoproject.com/wiki/DevelopersForHire
|
||||
|
|
|
@ -10,8 +10,8 @@ How do I get started?
|
|||
#. Check out the rest of the :doc:`documentation </index>`, and `ask questions`_ if you
|
||||
run into trouble.
|
||||
|
||||
.. _`Download the code`: http://www.djangoproject.com/download/
|
||||
.. _ask questions: http://www.djangoproject.com/community/
|
||||
.. _`Download the code`: https://www.djangoproject.com/download/
|
||||
.. _ask questions: https://www.djangoproject.com/community/
|
||||
|
||||
What are Django's prerequisites?
|
||||
--------------------------------
|
||||
|
@ -33,7 +33,7 @@ also need a database engine. PostgreSQL_ is recommended, because we're
|
|||
PostgreSQL fans, and MySQL_, `SQLite 3`_, and Oracle_ are also supported.
|
||||
|
||||
.. _Python: http://www.python.org/
|
||||
.. _server arrangements wiki page: http://code.djangoproject.com/wiki/ServerArrangements
|
||||
.. _server arrangements wiki page: https://code.djangoproject.com/wiki/ServerArrangements
|
||||
.. _PostgreSQL: http://www.postgresql.org/
|
||||
.. _MySQL: http://www.mysql.com/
|
||||
.. _`SQLite 3`: http://www.sqlite.org/
|
||||
|
@ -96,7 +96,7 @@ Will Django run under shared hosting (like TextDrive or Dreamhost)?
|
|||
|
||||
See our `Django-friendly Web hosts`_ page.
|
||||
|
||||
.. _`Django-friendly Web hosts`: http://code.djangoproject.com/wiki/DjangoFriendlyWebHosts
|
||||
.. _`Django-friendly Web hosts`: https://code.djangoproject.com/wiki/DjangoFriendlyWebHosts
|
||||
|
||||
Should I use the stable version or development version?
|
||||
-------------------------------------------------------
|
||||
|
|
|
@ -60,7 +60,7 @@ Glossary
|
|||
|
||||
.. parsed-literal::
|
||||
|
||||
http://www.djangoproject.com/weblog/2008/apr/12/**spring**/
|
||||
https://www.djangoproject.com/weblog/2008/apr/12/**spring**/
|
||||
|
||||
the last bit (``spring``) is the slug.
|
||||
|
||||
|
|
|
@ -30,4 +30,4 @@ you quickly accomplish common tasks.
|
|||
global Django community. Many writers in the aggregator write this sort of
|
||||
how-to material.
|
||||
|
||||
.. _django community aggregator: http://www.djangoproject.com/community/
|
||||
.. _django community aggregator: https://www.djangoproject.com/community/
|
||||
|
|
|
@ -29,7 +29,7 @@ Having trouble? We'd like to help!
|
|||
.. _post a question: http://groups.google.com/group/django-users/
|
||||
.. _#django IRC channel: irc://irc.freenode.net/django
|
||||
.. _IRC logs: http://django-irc-logs.com/
|
||||
.. _ticket tracker: http://code.djangoproject.com/
|
||||
.. _ticket tracker: https://code.djangoproject.com/
|
||||
|
||||
First steps
|
||||
===========
|
||||
|
|
|
@ -207,7 +207,7 @@ or contentious issues -- including, most notably, votes on new core
|
|||
committers -- may be held in private.
|
||||
|
||||
|
||||
.. _searching: http://code.djangoproject.com/search
|
||||
.. _searching: https://code.djangoproject.com/search
|
||||
.. _custom queries: https://code.djangoproject.com/query
|
||||
.. _django-developers: http://groups.google.com/group/django-developers
|
||||
.. _django-users: http://groups.google.com/group/django-users
|
||||
|
|
|
@ -140,4 +140,4 @@ discovered, please follow these guidelines:
|
|||
branch without permission if the commit breaks the release branch.
|
||||
|
||||
.. _django-developers: http://groups.google.com/group/django-developers
|
||||
.. _ticket tracker: http://code.djangoproject.com/newticket
|
||||
.. _ticket tracker: https://code.djangoproject.com/newticket
|
||||
|
|
|
@ -62,8 +62,8 @@ Browse the following sections to find out how:
|
|||
.. _django-users: http://groups.google.com/group/django-users
|
||||
.. _posting guidelines: https://code.djangoproject.com/wiki/UsingTheMailingList
|
||||
.. _#django IRC channel: irc://irc.freenode.net/django
|
||||
.. _community page: http://www.djangoproject.com/community/
|
||||
.. _register it here: http://www.djangoproject.com/community/add/blogs/
|
||||
.. _community page: https://www.djangoproject.com/community/
|
||||
.. _register it here: https://www.djangoproject.com/community/add/blogs/
|
||||
.. _django-developers: http://groups.google.com/group/django-developers
|
||||
.. _ticket tracker: http://code.djangoproject.com/newticket
|
||||
.. _easy pickings: http://code.djangoproject.com/query?status=!closed&easy=1
|
||||
.. _ticket tracker: https://code.djangoproject.com/newticket
|
||||
.. _easy pickings: https://code.djangoproject.com/query?status=!closed&easy=1
|
||||
|
|
|
@ -49,9 +49,9 @@ Start with these easy tasks to discover Django's development process.
|
|||
several that are useful for triaging tickets and reviewing patches as
|
||||
suggested above.
|
||||
|
||||
.. _reports page: http://code.djangoproject.com/wiki/Reports
|
||||
.. _reports page: https://code.djangoproject.com/wiki/Reports
|
||||
|
||||
.. _unreviewed ticket: http://code.djangoproject.com/query?status=!closed&stage=Unreviewed
|
||||
.. _unreviewed ticket: https://code.djangoproject.com/query?status=!closed&stage=Unreviewed
|
||||
|
||||
|
||||
Guidelines
|
||||
|
@ -118,7 +118,7 @@ some advice to make your work on Django more useful and rewarding.
|
|||
writing the very first tests for that feature, not that you get a pass from
|
||||
writing tests altogether.
|
||||
|
||||
.. _easy pickings: http://code.djangoproject.com/query?status=!closed&easy=1
|
||||
.. _easy pickings: https://code.djangoproject.com/query?status=!closed&easy=1
|
||||
|
||||
.. _new-contributors-faq:
|
||||
|
||||
|
|
|
@ -361,7 +361,7 @@ Then, you can help out by:
|
|||
|
||||
You can also find more :doc:`new-contributors`.
|
||||
|
||||
.. _Reports page: http://code.djangoproject.com/wiki/Reports
|
||||
.. _Reports page: https://code.djangoproject.com/wiki/Reports
|
||||
|
||||
However, we do ask the following of all general community members working in
|
||||
the ticket database:
|
||||
|
@ -384,10 +384,10 @@ the ticket database:
|
|||
or post a message to `django-developers`_. It's okay to be unsure,
|
||||
but your input is still valuable.
|
||||
|
||||
.. _Trac: http://code.djangoproject.com/
|
||||
.. _Trac: https://code.djangoproject.com/
|
||||
.. _django-developers: http://groups.google.com/group/django-developers
|
||||
.. _i18n branch: http://code.djangoproject.com/browser/django/branches/i18n
|
||||
.. _`tags/releases`: http://code.djangoproject.com/browser/django/tags/releases
|
||||
.. _`easy pickings`: http://code.djangoproject.com/query?status=!closed&easy=1
|
||||
.. _`creating an account on Trac`: http://www.djangoproject.com/accounts/register/
|
||||
.. _password reset page: http://www.djangoproject.com/accounts/password/reset/
|
||||
.. _i18n branch: https://code.djangoproject.com/browser/django/branches/i18n
|
||||
.. _`tags/releases`: https://code.djangoproject.com/browser/django/tags/releases
|
||||
.. _`easy pickings`: https://code.djangoproject.com/query?status=!closed&easy=1
|
||||
.. _`creating an account on Trac`: https://www.djangoproject.com/accounts/register/
|
||||
.. _password reset page: https://www.djangoproject.com/accounts/password/reset/
|
||||
|
|
|
@ -43,7 +43,7 @@ for feature branches:
|
|||
.. _git: http://git-scm.com/
|
||||
.. _mercurial: http://mercurial.selenic.com/
|
||||
.. _bazaar: http://bazaar.canonical.com/
|
||||
.. _django branches: http://code.djangoproject.com/wiki/DjangoBranches
|
||||
.. _django branches: https://code.djangoproject.com/wiki/DjangoBranches
|
||||
|
||||
Branch rules
|
||||
------------
|
||||
|
@ -104,7 +104,7 @@ To get the latest version of a branch's code, check it out using Subversion:
|
|||
|
||||
.. code-block:: bash
|
||||
|
||||
svn co http://code.djangoproject.com/svn/django/branches/<branch>/
|
||||
svn co https://code.djangoproject.com/svn/django/branches/<branch>/
|
||||
|
||||
...where ``<branch>`` is the branch's name. See the `list of branch names`_.
|
||||
|
||||
|
@ -114,7 +114,7 @@ conversion, execute this command from within your ``django`` directory:
|
|||
|
||||
.. code-block:: bash
|
||||
|
||||
svn switch http://code.djangoproject.com/svn/django/branches/<branch>/
|
||||
svn switch https://code.djangoproject.com/svn/django/branches/<branch>/
|
||||
|
||||
The advantage of using ``svn switch`` instead of ``svn co`` is that the
|
||||
``switch`` command retains any changes you might have made to your local copy
|
||||
|
@ -125,7 +125,7 @@ disadvantage is that it may cause conflicts with your local changes if the
|
|||
(Note that if you use ``svn switch``, you don't need to point Python at the
|
||||
new version, as explained in the next section.)
|
||||
|
||||
.. _list of branch names: http://code.djangoproject.com/browser/django/branches
|
||||
.. _list of branch names: https://code.djangoproject.com/browser/django/branches
|
||||
|
||||
.. _pointing-python-at-the-new-django-version:
|
||||
|
||||
|
@ -156,12 +156,12 @@ uncomment the line for the branch you want to use ('trunk' in this example) and
|
|||
make sure all other lines are commented::
|
||||
|
||||
# Trunk is a svn checkout of:
|
||||
# http://code.djangoproject.com/svn/django/trunk/
|
||||
# https://code.djangoproject.com/svn/django/trunk/
|
||||
#
|
||||
/path/to/trunk
|
||||
|
||||
# <branch> is a svn checkout of:
|
||||
# http://code.djangoproject.com/svn/django/branches/<branch>/
|
||||
# https://code.djangoproject.com/svn/django/branches/<branch>/
|
||||
#
|
||||
#/path/to/<branch>
|
||||
|
||||
|
|
|
@ -162,5 +162,5 @@ minified scripts when submitting patches for Django's javascript.
|
|||
|
||||
.. _Closure Compiler: http://code.google.com/closure/compiler/
|
||||
.. _django-developers: http://groups.google.com/group/django-developers
|
||||
.. _list of tickets with patches: http://code.djangoproject.com/query?status=new&status=assigned&status=reopened&has_patch=1&order=priority
|
||||
.. _ticket tracker: http://code.djangoproject.com/newticket
|
||||
.. _list of tickets with patches: https://code.djangoproject.com/query?status=new&status=assigned&status=reopened&has_patch=1&order=priority
|
||||
.. _ticket tracker: https://code.djangoproject.com/newticket
|
||||
|
|
|
@ -12,7 +12,7 @@ repository. This document covers the way the code repository is laid
|
|||
out and how to work with and find things in it.
|
||||
|
||||
|
||||
.. _an official packaged release of Django: http://www.djangoproject.com/download/
|
||||
.. _an official packaged release of Django: https://www.djangoproject.com/download/
|
||||
|
||||
|
||||
High-level overview
|
||||
|
@ -27,13 +27,13 @@ systems, and `a free online book`_ is available to help you get up to
|
|||
speed with using Subversion.
|
||||
|
||||
The Django Subversion repository is located online at
|
||||
`code.djangoproject.com/svn <http://code.djangoproject.com/svn/>`_. `A
|
||||
`code.djangoproject.com/svn <https://code.djangoproject.com/svn/>`_. `A
|
||||
friendly Web-based interface for browsing the code`_ is also
|
||||
available, though when using Subversion you'll always want to use the
|
||||
repository address instead. At the top level of the repository are two
|
||||
directories: ``django`` contains the full source code for all Django
|
||||
releases, while ``djangoproject.com`` contains the source code and
|
||||
templates for the `djangoproject.com <http://www.djangoproject.com/>`_
|
||||
templates for the `djangoproject.com <https://www.djangoproject.com/>`_
|
||||
Web site. For trying out in-development Django code, or contributing
|
||||
to Django, you'll always want to check out code from some location in
|
||||
the ``django`` directory.
|
||||
|
@ -58,7 +58,7 @@ into three areas:
|
|||
|
||||
.. _Subversion: http://subversion.tigris.org/
|
||||
.. _a free online book: http://svnbook.red-bean.com/
|
||||
.. _A friendly Web-based interface for browsing the code: http://code.djangoproject.com/browser/
|
||||
.. _A friendly Web-based interface for browsing the code: https://code.djangoproject.com/browser/
|
||||
|
||||
|
||||
Working with Django's trunk
|
||||
|
@ -70,7 +70,7 @@ developing new features, you'll want to get the code from trunk. You
|
|||
can get a complete copy of this code (a "Subversion checkout") by
|
||||
typing::
|
||||
|
||||
svn co http://code.djangoproject.com/svn/django/trunk/
|
||||
svn co https://code.djangoproject.com/svn/django/trunk/
|
||||
|
||||
Note that this will get *all* of Django: in addition to the top-level
|
||||
``django`` module containing Python code, you'll also get a copy of
|
||||
|
|
|
@ -320,5 +320,5 @@ The next obvious steps are for you to `download Django`_, read :doc:`the
|
|||
tutorial </intro/tutorial01>` and join `the community`_. Thanks for your
|
||||
interest!
|
||||
|
||||
.. _download Django: http://www.djangoproject.com/download/
|
||||
.. _the community: http://www.djangoproject.com/community/
|
||||
.. _download Django: https://www.djangoproject.com/download/
|
||||
.. _the community: https://www.djangoproject.com/community/
|
||||
|
|
|
@ -96,7 +96,7 @@ Django's documentation is kept in the same source control system as its code. It
|
|||
lives in the `django/trunk/docs`_ directory of our Subversion repository. Each
|
||||
document online is a separate text file in the repository.
|
||||
|
||||
.. _django/trunk/docs: http://code.djangoproject.com/browser/django/trunk/docs
|
||||
.. _django/trunk/docs: https://code.djangoproject.com/browser/django/trunk/docs
|
||||
|
||||
Where to get it
|
||||
===============
|
||||
|
@ -124,7 +124,7 @@ rather than asking broad tech-support questions. If you need help with your
|
|||
particular Django setup, try the `django-users mailing list`_ or the `#django
|
||||
IRC channel`_ instead.
|
||||
|
||||
.. _ticket system: http://code.djangoproject.com/simpleticket?component=Documentation
|
||||
.. _ticket system: https://code.djangoproject.com/simpleticket?component=Documentation
|
||||
.. _django-users mailing list: http://groups.google.com/group/django-users
|
||||
.. _#django IRC channel: irc://irc.freenode.net/django
|
||||
|
||||
|
@ -148,7 +148,7 @@ shell command:
|
|||
|
||||
.. code-block:: bash
|
||||
|
||||
$ svn co http://code.djangoproject.com/svn/django/trunk/docs/ django_docs
|
||||
$ svn co https://code.djangoproject.com/svn/django/trunk/docs/ django_docs
|
||||
|
||||
One low-tech way of taking advantage of the text documentation is by using the
|
||||
Unix ``grep`` utility to search for a phrase in all of the documentation. For
|
||||
|
|
|
@ -14,7 +14,7 @@ directory containing the profiling logfiles.
|
|||
.SH "SEE ALSO"
|
||||
Discussion of profiling Django applications on the Django project's wiki:
|
||||
.sp
|
||||
.I http://www.djangoproject.com/wiki/ProfilingDjango
|
||||
.I https://www.djangoproject.com/wiki/ProfilingDjango
|
||||
|
||||
.SH "AUTHORS/CREDITS"
|
||||
Originally developed at World Online in Lawrence, Kansas, USA. Refer to the
|
||||
|
|
|
@ -19,7 +19,7 @@ you're using a Linux distro and don't know how to find out if a package
|
|||
is available, then now is a good time to learn. The Django Wiki contains
|
||||
a list of `Third Party Distributions`_ to help you out.
|
||||
|
||||
.. _`Third Party Distributions`: http://code.djangoproject.com/wiki/Distributions
|
||||
.. _`Third Party Distributions`: https://code.djangoproject.com/wiki/Distributions
|
||||
|
||||
|
||||
For distributors
|
||||
|
|
|
@ -350,7 +350,7 @@ a "reverse" generic relationship to enable an additional API. For example::
|
|||
``Bookmark`` instances will each have a ``tags`` attribute, which can
|
||||
be used to retrieve their associated ``TaggedItems``::
|
||||
|
||||
>>> b = Bookmark(url='http://www.djangoproject.com/')
|
||||
>>> b = Bookmark(url='https://www.djangoproject.com/')
|
||||
>>> b.save()
|
||||
>>> t1 = TaggedItem(content_object=b, tag='django')
|
||||
>>> t1.save()
|
||||
|
@ -377,7 +377,7 @@ referred to above used fields named ``content_type_fk`` and
|
|||
Of course, if you don't add the reverse relationship, you can do the
|
||||
same types of lookups manually::
|
||||
|
||||
>>> b = Bookmark.objects.get(url='http://www.djangoproject.com/')
|
||||
>>> b = Bookmark.objects.get(url='https://www.djangoproject.com/')
|
||||
>>> bookmark_type = ContentType.objects.get_for_model(b)
|
||||
>>> TaggedItem.objects.filter(content_type__pk=bookmark_type.id,
|
||||
... object_id=b.id)
|
||||
|
|
|
@ -147,7 +147,7 @@ Via the Python API
|
|||
which lives in `django/contrib/flatpages/models.py`_. You can access
|
||||
flatpage objects via the :doc:`Django database API </topics/db/queries>`.
|
||||
|
||||
.. _django/contrib/flatpages/models.py: http://code.djangoproject.com/browser/django/trunk/django/contrib/flatpages/models.py
|
||||
.. _django/contrib/flatpages/models.py: https://code.djangoproject.com/browser/django/trunk/django/contrib/flatpages/models.py
|
||||
|
||||
.. currentmodule:: django.contrib.flatpages
|
||||
|
||||
|
|
|
@ -215,7 +215,7 @@ Then distance queries may be performed as follows::
|
|||
>>> qs = SouthTexasCity.objects.filter(point__distance_gte=(pnt, D(mi=20)))
|
||||
>>> qs = SouthTexasCity.objects.filter(point__distance_gte=(pnt, D(chain=100)))
|
||||
|
||||
__ http://code.djangoproject.com/browser/django/trunk/django/contrib/gis/tests/distapp/models.py
|
||||
__ https://code.djangoproject.com/browser/django/trunk/django/contrib/gis/tests/distapp/models.py
|
||||
|
||||
.. _compatibility-table:
|
||||
|
||||
|
|
|
@ -736,7 +736,7 @@ the distance from the `Tasmanian`__ city of Hobart to every other
|
|||
in kilometers. See the :ref:`ref-measure` for usage details and the list of
|
||||
:ref:`supported_units`.
|
||||
|
||||
__ http://code.djangoproject.com/browser/django/trunk/django/contrib/gis/tests/distapp/models.py
|
||||
__ https://code.djangoproject.com/browser/django/trunk/django/contrib/gis/tests/distapp/models.py
|
||||
__ http://en.wikipedia.org/wiki/Tasmania
|
||||
|
||||
``length``
|
||||
|
|
|
@ -666,7 +666,7 @@ community! You can:
|
|||
and specify the component as "GIS".
|
||||
|
||||
__ http://groups.google.com/group/geodjango
|
||||
__ http://code.djangoproject.com/simpleticket
|
||||
__ https://code.djangoproject.com/simpleticket
|
||||
|
||||
.. _libsettings:
|
||||
|
||||
|
|
|
@ -156,7 +156,7 @@ any code you'd like to contribute. One thing we ask is that you please use
|
|||
Unicode objects (``u'mystring'``) for strings, rather than setting the encoding
|
||||
in the file. See any of the existing flavors for examples.
|
||||
|
||||
.. _create a ticket: http://code.djangoproject.com/simpleticket
|
||||
.. _create a ticket: https://code.djangoproject.com/simpleticket
|
||||
|
||||
Localflavor and backwards compatibility
|
||||
=======================================
|
||||
|
|
|
@ -67,4 +67,4 @@ Via the Python API
|
|||
which lives in `django/contrib/redirects/models.py`_. You can access redirect
|
||||
objects via the :doc:`Django database API </topics/db/queries>`.
|
||||
|
||||
.. _django/contrib/redirects/models.py: http://code.djangoproject.com/browser/django/trunk/django/contrib/redirects/models.py
|
||||
.. _django/contrib/redirects/models.py: https://code.djangoproject.com/browser/django/trunk/django/contrib/redirects/models.py
|
||||
|
|
|
@ -901,7 +901,7 @@ For example, to create an Atom 1.0 feed and print it to standard output::
|
|||
...
|
||||
</feed>
|
||||
|
||||
.. _django/utils/feedgenerator.py: http://code.djangoproject.com/browser/django/trunk/django/utils/feedgenerator.py
|
||||
.. _django/utils/feedgenerator.py: https://code.djangoproject.com/browser/django/trunk/django/utils/feedgenerator.py
|
||||
|
||||
.. currentmodule:: django.contrib.syndication
|
||||
|
||||
|
|
|
@ -345,7 +345,7 @@ storage engine, you have a couple of options.
|
|||
* Another method for changing the storage engine is described in
|
||||
AlterModelOnSyncDB_.
|
||||
|
||||
.. _AlterModelOnSyncDB: http://code.djangoproject.com/wiki/AlterModelOnSyncDB
|
||||
.. _AlterModelOnSyncDB: https://code.djangoproject.com/wiki/AlterModelOnSyncDB
|
||||
|
||||
Table names
|
||||
-----------
|
||||
|
@ -455,7 +455,7 @@ Versions of SQLite 3.3.5 and older contains the following bugs:
|
|||
DecimalFields.
|
||||
|
||||
.. _handling: http://www.sqlite.org/cvstrac/tktview?tn=1768
|
||||
.. _aggregation: http://code.djangoproject.com/ticket/10031
|
||||
.. _aggregation: https://code.djangoproject.com/ticket/10031
|
||||
|
||||
SQLite 3.3.6 was released in April 2006, so most current binary distributions
|
||||
for different platforms include newer version of SQLite usable from Python
|
||||
|
|
|
@ -806,7 +806,7 @@ It is also important to remember that when running with :setting:`DEBUG`
|
|||
turned on, Django will remember every SQL query it executes. This is useful
|
||||
when you're debugging, but it'll rapidly consume memory on a production server.
|
||||
|
||||
.. _django/views/debug.py: http://code.djangoproject.com/browser/django/trunk/django/views/debug.py
|
||||
.. _django/views/debug.py: https://code.djangoproject.com/browser/django/trunk/django/views/debug.py
|
||||
|
||||
DEBUG_PROPAGATE_EXCEPTIONS
|
||||
--------------------------
|
||||
|
@ -1237,7 +1237,7 @@ and including a copy here would inevitably become rapidly out of date. You can
|
|||
see the current list of translated languages by looking in
|
||||
``django/conf/global_settings.py`` (or view the `online source`_).
|
||||
|
||||
.. _online source: http://code.djangoproject.com/browser/django/trunk/django/conf/global_settings.py
|
||||
.. _online source: https://code.djangoproject.com/browser/django/trunk/django/conf/global_settings.py
|
||||
|
||||
The list is a tuple of two-tuples in the format ``(language code, language
|
||||
name)``, the ``language code`` part should be a
|
||||
|
@ -2151,7 +2151,7 @@ to ensure your processes are running in the correct environment.
|
|||
URL_VALIDATOR_USER_AGENT
|
||||
------------------------
|
||||
|
||||
Default: ``Django/<version> (http://www.djangoproject.com/)``
|
||||
Default: ``Django/<version> (https://www.djangoproject.com/)``
|
||||
|
||||
The string to use as the ``User-Agent`` header when checking to see if
|
||||
URLs exist (see the ``verify_exists`` option on
|
||||
|
|
|
@ -98,7 +98,7 @@ to, or in lieu of custom ``field.clean()`` methods.
|
|||
:param verify_exists: Sets :attr:`verify_exists`. Defaults to ``False``.
|
||||
:param validator_user_agent: Sets :attr:`validator_user_agent`. Defaults to
|
||||
:setting:`URL_VALIDATOR_USER_AGENT` or, if that setting is set to a
|
||||
null value, ``"Django (http://www.djangoproject.com/)"``.
|
||||
null value, ``"Django (https://www.djangoproject.com/)"``.
|
||||
|
||||
.. attribute:: verify_exists
|
||||
|
||||
|
|
|
@ -91,8 +91,8 @@ reasonably routine and only need to be done once. A list of the necessary
|
|||
changes is described in the `Removing The Magic`_ wiki page. There is also an
|
||||
easy checklist_ for reference when undertaking the porting operation.
|
||||
|
||||
.. _Removing The Magic: http://code.djangoproject.com/wiki/RemovingTheMagic
|
||||
.. _checklist: http://code.djangoproject.com/wiki/MagicRemovalCheatSheet
|
||||
.. _Removing The Magic: https://code.djangoproject.com/wiki/RemovingTheMagic
|
||||
.. _checklist: https://code.djangoproject.com/wiki/MagicRemovalCheatSheet
|
||||
|
||||
Problem reports and getting help
|
||||
================================
|
||||
|
@ -113,7 +113,7 @@ there's a #django channel on irc.freenode.net that is regularly populated by
|
|||
Django users and developers from around the world. Friendly people are usually
|
||||
available at any hour of the day -- to help, or just to chat.
|
||||
|
||||
.. _Django Web site: http://www.djangoproject.com/
|
||||
.. _Django Web site: https://www.djangoproject.com/
|
||||
.. _django-users: http://groups.google.com/group/django-users
|
||||
|
||||
Thanks for using Django!
|
||||
|
|
|
@ -253,4 +253,4 @@ all their hard work:
|
|||
that went into 0.96 -- but everyone who's contributed to Django is listed
|
||||
in AUTHORS_.
|
||||
|
||||
.. _AUTHORS: http://code.djangoproject.com/browser/django/trunk/AUTHORS
|
||||
.. _AUTHORS: https://code.djangoproject.com/browser/django/trunk/AUTHORS
|
||||
|
|
|
@ -57,7 +57,7 @@ An improved Django ORM
|
|||
features opened up by this refactoring, is available on the Django
|
||||
wiki:
|
||||
|
||||
* http://code.djangoproject.com/wiki/QuerysetRefactorBranch
|
||||
* https://code.djangoproject.com/wiki/QuerysetRefactorBranch
|
||||
|
||||
Automatic escaping of template variables
|
||||
To provide improved security against cross-site scripting (XSS)
|
||||
|
@ -84,7 +84,7 @@ Django 1.0 release, and a comprehensive list of backwards-incompatible
|
|||
changes is also available on the Django wiki for those who want to
|
||||
begin developing and testing their upgrade process:
|
||||
|
||||
* http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges
|
||||
* https://code.djangoproject.com/wiki/BackwardsIncompatibleChanges
|
||||
|
||||
|
||||
The Django 1.0 roadmap
|
||||
|
@ -123,7 +123,7 @@ Of course, like any estimated timeline, this is subject to change as
|
|||
requirements dictate. The latest information will always be available
|
||||
on the Django project wiki:
|
||||
|
||||
* http://code.djangoproject.com/wiki/VersionOneRoadmap
|
||||
* https://code.djangoproject.com/wiki/VersionOneRoadmap
|
||||
|
||||
|
||||
What you can do to help
|
||||
|
@ -136,7 +136,7 @@ codebase in a safe test environment and reporting any bugs or issues
|
|||
you encounter. The Django ticket tracker is the central place to
|
||||
search for open issues:
|
||||
|
||||
* http://code.djangoproject.com/timeline
|
||||
* https://code.djangoproject.com/timeline
|
||||
|
||||
Please open new tickets if no existing ticket corresponds to a problem
|
||||
you're running into.
|
||||
|
|
|
@ -98,7 +98,7 @@ Of course, like any estimated timeline, this is subject to change as
|
|||
requirements dictate. The latest information will always be available
|
||||
on the Django project wiki:
|
||||
|
||||
* http://code.djangoproject.com/wiki/VersionOneRoadmap
|
||||
* https://code.djangoproject.com/wiki/VersionOneRoadmap
|
||||
|
||||
|
||||
What you can do to help
|
||||
|
@ -111,7 +111,7 @@ codebase in a safe test environment and reporting any bugs or issues
|
|||
you encounter. The Django ticket tracker is the central place to
|
||||
search for open issues:
|
||||
|
||||
* http://code.djangoproject.com/timeline
|
||||
* https://code.djangoproject.com/timeline
|
||||
|
||||
Please open new tickets if no existing ticket corresponds to a problem
|
||||
you're running into.
|
||||
|
|
|
@ -94,7 +94,7 @@ codebase in a safe test environment and reporting any bugs or issues
|
|||
you encounter. The Django ticket tracker is the central place to
|
||||
search for open issues:
|
||||
|
||||
* http://code.djangoproject.com/timeline
|
||||
* https://code.djangoproject.com/timeline
|
||||
|
||||
Please open new tickets if no existing ticket corresponds to a problem
|
||||
you're running into.
|
||||
|
|
|
@ -79,7 +79,7 @@ been improved and the method by which Django generates unique session
|
|||
identifiers has been made much more robust.
|
||||
|
||||
.. _the documentation for generic relations: ../contenttypes/#generic-relations
|
||||
.. _the Django wiki: http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#Removedseveralmoredeprecatedfeaturesfor1.0
|
||||
.. _the Django wiki: https://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#Removedseveralmoredeprecatedfeaturesfor1.0
|
||||
|
||||
|
||||
The Django 1.0 roadmap
|
||||
|
@ -115,7 +115,7 @@ Of course, like any estimated timeline, this is subject to change as
|
|||
requirements dictate. The latest information will always be available
|
||||
on the Django project wiki:
|
||||
|
||||
* http://code.djangoproject.com/wiki/VersionOneRoadmap
|
||||
* https://code.djangoproject.com/wiki/VersionOneRoadmap
|
||||
|
||||
|
||||
What you can do to help
|
||||
|
@ -128,7 +128,7 @@ codebase in a safe test environment and reporting any bugs or issues
|
|||
you encounter. The Django ticket tracker is the central place to
|
||||
search for open issues:
|
||||
|
||||
* http://code.djangoproject.com/timeline
|
||||
* https://code.djangoproject.com/timeline
|
||||
|
||||
Please open new tickets if no existing ticket corresponds to a problem
|
||||
you're running into.
|
||||
|
|
|
@ -213,7 +213,7 @@ New (1.0)::
|
|||
* The new admin comes with a ton of new features; you can read about them in
|
||||
the :doc:`admin documentation </ref/contrib/admin/index>`.
|
||||
|
||||
__ http://code.djangoproject.com/wiki/NewformsAdminBranch
|
||||
__ https://code.djangoproject.com/wiki/NewformsAdminBranch
|
||||
|
||||
URLs
|
||||
----
|
||||
|
|
|
@ -61,4 +61,4 @@ highlights:
|
|||
documentation, including both corrections to existing documents and
|
||||
expanded and new documentation.
|
||||
|
||||
.. _the Subversion log of the 1.0.X branch: http://code.djangoproject.com/log/django/branches/releases/1.0.X
|
||||
.. _the Subversion log of the 1.0.X branch: https://code.djangoproject.com/log/django/branches/releases/1.0.X
|
||||
|
|
|
@ -42,7 +42,7 @@ detailed porting guide:
|
|||
1.0-porting-guide
|
||||
|
||||
A complete list of backwards-incompatible changes can be found at
|
||||
http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges.
|
||||
https://code.djangoproject.com/wiki/BackwardsIncompatibleChanges.
|
||||
|
||||
What's new in Django 1.0
|
||||
========================
|
||||
|
@ -109,7 +109,7 @@ the ORM's internals. A guide to the changes, including backwards-incompatible
|
|||
modifications and mentions of new features opened up by this refactoring, is
|
||||
`available on the Django wiki`__.
|
||||
|
||||
__ http://code.djangoproject.com/wiki/QuerysetRefactorBranch
|
||||
__ https://code.djangoproject.com/wiki/QuerysetRefactorBranch
|
||||
|
||||
Automatic escaping of template variables
|
||||
----------------------------------------
|
||||
|
|
|
@ -134,7 +134,7 @@ Django team by trying out the alpha codebase in a safe test environment and
|
|||
reporting any bugs or issues you encounter. The Django ticket tracker is the
|
||||
central place to search for open issues:
|
||||
|
||||
* http://code.djangoproject.com/timeline
|
||||
* https://code.djangoproject.com/timeline
|
||||
|
||||
Please open new tickets if no existing ticket corresponds to a problem you're
|
||||
running into.
|
||||
|
|
|
@ -179,7 +179,7 @@ Django team by trying out the beta codebase in a safe test environment and
|
|||
reporting any bugs or issues you encounter. The Django ticket tracker is the
|
||||
central place to search for open issues:
|
||||
|
||||
* http://code.djangoproject.com/timeline
|
||||
* https://code.djangoproject.com/timeline
|
||||
|
||||
Please open new tickets if no existing ticket corresponds to a problem you're
|
||||
running into.
|
||||
|
|
|
@ -84,7 +84,7 @@ release candidate in a safe testing environment and reporting any bugs
|
|||
or issues you encounter. The Django ticket tracker is the central
|
||||
place to search for open issues:
|
||||
|
||||
* http://code.djangoproject.com/timeline
|
||||
* https://code.djangoproject.com/timeline
|
||||
|
||||
Please open a new ticket only if no existing ticket corresponds to a
|
||||
problem you're running into.
|
||||
|
|
|
@ -101,7 +101,7 @@ If you've been relying on this middleware, the easiest upgrade path is:
|
|||
* Introduce your modified version of ``SetRemoteAddrFromForwardedFor`` as a
|
||||
piece of middleware in your own project.
|
||||
|
||||
__ http://code.djangoproject.com/browser/django/trunk/django/middleware/http.py?rev=11000#L33
|
||||
__ https://code.djangoproject.com/browser/django/trunk/django/middleware/http.py?rev=11000#L33
|
||||
|
||||
Names of uploaded files are available later
|
||||
-------------------------------------------
|
||||
|
|
|
@ -559,7 +559,7 @@ Django team by trying out the alpha codebase in a safe test environment and
|
|||
reporting any bugs or issues you encounter. The Django ticket tracker is the
|
||||
central place to search for open issues:
|
||||
|
||||
* http://code.djangoproject.com/timeline
|
||||
* https://code.djangoproject.com/timeline
|
||||
|
||||
Please open new tickets if no existing ticket corresponds to a problem you're
|
||||
running into.
|
||||
|
|
|
@ -143,7 +143,7 @@ codebase in a safe test environment and reporting any bugs or issues
|
|||
you encounter. The Django ticket tracker is the central place to
|
||||
search for open issues:
|
||||
|
||||
* http://code.djangoproject.com/timeline
|
||||
* https://code.djangoproject.com/timeline
|
||||
|
||||
Please open new tickets if no existing ticket corresponds to a problem
|
||||
you're running into.
|
||||
|
|
|
@ -76,7 +76,7 @@ release candidate in a safe testing environment and reporting any bugs
|
|||
or issues you encounter. The Django ticket tracker is the central
|
||||
place to search for open issues:
|
||||
|
||||
* http://code.djangoproject.com/timeline
|
||||
* https://code.djangoproject.com/timeline
|
||||
|
||||
Please open a new ticket only if no existing ticket corresponds to a
|
||||
problem you're running into.
|
||||
|
|
|
@ -70,7 +70,7 @@ not be concerned about the data loss bug, or the manual configuration of
|
|||
documentation on :ref:`controlling the creation order of test
|
||||
databases <topics-testing-creation-dependencies>` for details.
|
||||
|
||||
.. _original problem report: http://code.djangoproject.com/ticket/14415
|
||||
.. _original problem report: https://code.djangoproject.com/ticket/14415
|
||||
|
||||
GeoDjango
|
||||
=========
|
||||
|
|
|
@ -116,7 +116,7 @@ ModelAdmin.lookup_allowed signature changed
|
|||
|
||||
Django 1.2.4 introduced a method ``lookup_allowed`` on ``ModelAdmin``, to cope
|
||||
with a security issue (changeset `[15033]
|
||||
<http://code.djangoproject.com/changeset/15033>`_). Although this method was
|
||||
<https://code.djangoproject.com/changeset/15033>`_). Although this method was
|
||||
never documented, it seems some people have overridden ``lookup_allowed``,
|
||||
especially to cope with regressions introduced by that changeset. While the
|
||||
method is still undocumented and not marked as stable, it may be helpful to know
|
||||
|
|
|
@ -257,7 +257,7 @@ would be well advised to seek out a better, less naive approach to the
|
|||
problem.
|
||||
|
||||
.. _Scunthorpe problem: http://en.wikipedia.org/wiki/Scunthorpe_problem
|
||||
.. _commit that implemented this change: http://code.djangoproject.com/changeset/13996
|
||||
.. _commit that implemented this change: https://code.djangoproject.com/changeset/13996
|
||||
|
||||
Localflavor changes
|
||||
~~~~~~~~~~~~~~~~~~~
|
||||
|
@ -373,7 +373,7 @@ Django team by trying out the alpha codebase in a safe test environment and
|
|||
reporting any bugs or issues you encounter. The Django ticket tracker is the
|
||||
central place to search for open issues:
|
||||
|
||||
* http://code.djangoproject.com/timeline
|
||||
* https://code.djangoproject.com/timeline
|
||||
|
||||
Please open new tickets if no existing ticket corresponds to a problem you're
|
||||
running into.
|
||||
|
|
|
@ -135,7 +135,7 @@ form validation. The previously undocumented method
|
|||
in favor of a new :attr:`~django.contrib.admin.AdminSite.login_form`
|
||||
attribute.
|
||||
|
||||
.. _r12634: http://code.djangoproject.com/changeset/12634
|
||||
.. _r12634: https://code.djangoproject.com/changeset/12634
|
||||
|
||||
Changes to ``USStateField``
|
||||
===========================
|
||||
|
@ -209,7 +209,7 @@ Django team by trying out the beta codebase in a safe test environment and
|
|||
reporting any bugs or issues you encounter. The Django ticket tracker is the
|
||||
central place to search for open issues:
|
||||
|
||||
* http://code.djangoproject.com/timeline
|
||||
* https://code.djangoproject.com/timeline
|
||||
|
||||
Please open new tickets if no existing ticket corresponds to a problem you're
|
||||
running into.
|
||||
|
|
|
@ -346,7 +346,7 @@ verification. Consult :doc:`the Django CSRF documentation
|
|||
</ref/contrib/csrf>` for details on how to handle CSRF verification in
|
||||
AJAX requests.
|
||||
|
||||
.. _security issues: http://www.djangoproject.com/weblog/2011/feb/08/security/
|
||||
.. _security issues: https://www.djangoproject.com/weblog/2011/feb/08/security/
|
||||
|
||||
Restricted filters in admin interface
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
@ -464,7 +464,7 @@ would be well advised to seek out a better, less naive approach to the
|
|||
problem.
|
||||
|
||||
.. _Scunthorpe problem: http://en.wikipedia.org/wiki/Scunthorpe_problem
|
||||
.. _commit that implemented this change: http://code.djangoproject.com/changeset/13996
|
||||
.. _commit that implemented this change: https://code.djangoproject.com/changeset/13996
|
||||
|
||||
Localflavor changes
|
||||
~~~~~~~~~~~~~~~~~~~
|
||||
|
@ -791,7 +791,7 @@ form validation. The previously undocumented method
|
|||
in favor of a new :attr:`~django.contrib.admin.AdminSite.login_form`
|
||||
attribute.
|
||||
|
||||
.. _r12634: http://code.djangoproject.com/changeset/12634
|
||||
.. _r12634: https://code.djangoproject.com/changeset/12634
|
||||
|
||||
``reset`` and ``sqlreset`` management commands
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
|
|
@ -1095,7 +1095,7 @@ Django team by trying out the alpha codebase in a safe test environment and
|
|||
reporting any bugs or issues you encounter. The Django ticket tracker is the
|
||||
central place to search for open issues:
|
||||
|
||||
* http://code.djangoproject.com/timeline
|
||||
* https://code.djangoproject.com/timeline
|
||||
|
||||
Please open new tickets if no existing ticket corresponds to a problem you're
|
||||
running into.
|
||||
|
|
|
@ -619,7 +619,7 @@ Django 1.4 also includes several smaller improvements worth noting:
|
|||
``'API'``, ``'TOKEN'``, ``'KEY'`` were added, ``'PASSWORD'`` was changed to
|
||||
``'PASS'``.
|
||||
|
||||
.. _django/views/debug.py: http://code.djangoproject.com/browser/django/trunk/django/views/debug.py
|
||||
.. _django/views/debug.py: https://code.djangoproject.com/browser/django/trunk/django/views/debug.py
|
||||
|
||||
|
||||
Backwards incompatible changes in 1.4
|
||||
|
@ -1167,7 +1167,7 @@ Django team by trying out the beta codebase in a safe test environment and
|
|||
reporting any bugs or issues you encounter. The Django ticket tracker is the
|
||||
central place to search for open issues:
|
||||
|
||||
* http://code.djangoproject.com/timeline
|
||||
* https://code.djangoproject.com/timeline
|
||||
|
||||
Please open new tickets if no existing ticket corresponds to a problem you're
|
||||
running into.
|
||||
|
|
|
@ -1899,7 +1899,7 @@ A full authorization implementation can be found in
|
|||
`django/contrib/auth/backends.py`_, which is the default backend and queries
|
||||
the ``auth_permission`` table most of the time.
|
||||
|
||||
.. _django/contrib/auth/backends.py: http://code.djangoproject.com/browser/django/trunk/django/contrib/auth/backends.py
|
||||
.. _django/contrib/auth/backends.py: https://code.djangoproject.com/browser/django/trunk/django/contrib/auth/backends.py
|
||||
|
||||
.. _anonymous_auth:
|
||||
|
||||
|
|
|
@ -39,7 +39,7 @@ Django ships with generic views to do the following:
|
|||
|
||||
* Present date-based objects in year/month/day archive pages,
|
||||
associated detail, and "latest" pages.
|
||||
`The Django Weblog <http://www.djangoproject.com/weblog/>`_'s
|
||||
`The Django Weblog <https://www.djangoproject.com/weblog/>`_'s
|
||||
year, month, and day archives are built with these, as would be a typical
|
||||
newspaper's archives.
|
||||
|
||||
|
|
|
@ -24,7 +24,7 @@ The basics:
|
|||
examples`_. (In the Django source distribution, these examples are in the
|
||||
``tests/modeltests`` directory.)
|
||||
|
||||
.. _official repository of model examples: http://code.djangoproject.com/browser/django/trunk/tests/modeltests
|
||||
.. _official repository of model examples: https://code.djangoproject.com/browser/django/trunk/tests/modeltests
|
||||
|
||||
Quick example
|
||||
=============
|
||||
|
@ -328,7 +328,7 @@ whatever you want. For example::
|
|||
|
||||
For sample code, see the `Many-to-one relationship model tests`_.
|
||||
|
||||
.. _Many-to-one relationship model tests: http://code.djangoproject.com/browser/django/trunk/tests/modeltests/many_to_one
|
||||
.. _Many-to-one relationship model tests: https://code.djangoproject.com/browser/django/trunk/tests/modeltests/many_to_one
|
||||
|
||||
Many-to-many relationships
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
@ -378,7 +378,7 @@ form would let users select the toppings.
|
|||
|
||||
See the `Many-to-many relationship model example`_ for a full example.
|
||||
|
||||
.. _Many-to-many relationship model example: http://code.djangoproject.com/browser/django/trunk/tests/modeltests/many_to_many/models.py
|
||||
.. _Many-to-many relationship model example: https://code.djangoproject.com/browser/django/trunk/tests/modeltests/many_to_many/models.py
|
||||
|
||||
:class:`~django.db.models.ManyToManyField` fields also accept a number of extra
|
||||
arguments which are explained in :ref:`the model field reference
|
||||
|
@ -571,7 +571,7 @@ can be made; see :ref:`the model field reference <ref-onetoone>` for details.
|
|||
|
||||
See the `One-to-one relationship model example`_ for a full example.
|
||||
|
||||
.. _One-to-one relationship model example: http://code.djangoproject.com/browser/django/trunk/tests/modeltests/one_to_one/models.py
|
||||
.. _One-to-one relationship model example: https://code.djangoproject.com/browser/django/trunk/tests/modeltests/one_to_one/models.py
|
||||
|
||||
:class:`~django.db.models.OneToOneField` fields also accept one optional argument
|
||||
described in the :ref:`model field reference <ref-onetoone>`.
|
||||
|
|
|
@ -813,7 +813,7 @@ precede the definition of any keyword arguments. For example::
|
|||
The `OR lookups examples`_ in the Django unit tests show some possible uses
|
||||
of ``Q``.
|
||||
|
||||
.. _OR lookups examples: http://code.djangoproject.com/browser/django/trunk/tests/modeltests/or_lookups/tests.py
|
||||
.. _OR lookups examples: https://code.djangoproject.com/browser/django/trunk/tests/modeltests/or_lookups/tests.py
|
||||
|
||||
Comparing objects
|
||||
=================
|
||||
|
|
|
@ -38,7 +38,7 @@ Django ships with generic views to do the following:
|
|||
|
||||
* Present date-based objects in year/month/day archive pages,
|
||||
associated detail, and "latest" pages. The Django Weblog's
|
||||
(http://www.djangoproject.com/weblog/) year, month, and
|
||||
(https://www.djangoproject.com/weblog/) year, month, and
|
||||
day archives are built with these, as would be a typical
|
||||
newspaper's archives.
|
||||
|
||||
|
|
|
@ -485,7 +485,7 @@ that returns the url patterns available to that instance. It is this attribute
|
|||
that you ``include()`` into your projects ``urlpatterns`` when you deploy the
|
||||
admin instance.
|
||||
|
||||
.. _`Django Web site`: http://www.djangoproject.com/
|
||||
.. _`Django Web site`: https://www.djangoproject.com/
|
||||
|
||||
Captured parameters
|
||||
-------------------
|
||||
|
|
|
@ -72,7 +72,7 @@ installation instructions for each platform.
|
|||
.. _Apache: http://httpd.apache.org/
|
||||
.. _nginx: http://nginx.net/
|
||||
.. _mod_wsgi: http://code.google.com/p/modwsgi/
|
||||
.. _server-arrangements wiki page: http://code.djangoproject.com/wiki/ServerArrangements
|
||||
.. _server-arrangements wiki page: https://code.djangoproject.com/wiki/ServerArrangements
|
||||
|
||||
.. _database-installation:
|
||||
|
||||
|
@ -253,7 +253,7 @@ Installing an official release manually
|
|||
run the command ``python setup.py install``. This will install Django in
|
||||
your Python installation's ``site-packages`` directory.
|
||||
|
||||
.. _download page: http://www.djangoproject.com/download/
|
||||
.. _download page: https://www.djangoproject.com/download/
|
||||
.. _bsdtar: http://gnuwin32.sourceforge.net/packages/bsdtar.htm
|
||||
.. _7-zip: http://www.7-zip.org/
|
||||
|
||||
|
@ -273,8 +273,8 @@ Installing the development version
|
|||
(For stable releases, any necessary changes are documented in the
|
||||
release notes.)
|
||||
|
||||
.. _the development timeline: http://code.djangoproject.com/timeline
|
||||
.. _the list of backwards-incompatible changes: http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges
|
||||
.. _the development timeline: https://code.djangoproject.com/timeline
|
||||
.. _the list of backwards-incompatible changes: https://code.djangoproject.com/wiki/BackwardsIncompatibleChanges
|
||||
|
||||
If you'd like to be able to update your Django code occasionally with the
|
||||
latest bug fixes and improvements, follow these instructions:
|
||||
|
@ -290,7 +290,7 @@ latest bug fixes and improvements, follow these instructions:
|
|||
.. code-block:: bash
|
||||
|
||||
# Subversion
|
||||
svn co http://code.djangoproject.com/svn/django/trunk/ django-trunk
|
||||
svn co https://code.djangoproject.com/svn/django/trunk/ django-trunk
|
||||
|
||||
Mirrors of the Subversion repository can be obtained like so:
|
||||
|
||||
|
|
Loading…
Reference in New Issue