summaryrefslogtreecommitdiff
path: root/docs/topics/python3.txt
diff options
context:
space:
mode:
authorTim Graham <timograham@gmail.com>2016-05-08 18:07:43 -0400
committerTim Graham <timograham@gmail.com>2016-05-08 18:09:10 -0400
commit145572adb386dc05bc1302bee4432648b13e7e66 (patch)
treec16ab4d1b735d95ab51a845202330f268e7158f8 /docs/topics/python3.txt
parent86b346435a6735484c23fc9c798cf5243cbf8124 (diff)
[1.9.x] Fixed #26483 -- Updated docs.python.org links to use Intersphinx.
Backport of f5ff5010cd74500785a707ac70b51d292403cddc from master
Diffstat (limited to 'docs/topics/python3.txt')
-rw-r--r--docs/topics/python3.txt8
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/topics/python3.txt b/docs/topics/python3.txt
index 003dd0ebc5..04a975d8f2 100644
--- a/docs/topics/python3.txt
+++ b/docs/topics/python3.txt
@@ -16,9 +16,10 @@ Philosophy
==========
This document assumes that you are familiar with the changes between Python 2
-and Python 3. If you aren't, read `Python's official porting guide`_ first.
-Refreshing your knowledge of unicode handling on Python 2 and 3 will help; the
-`Pragmatic Unicode`_ presentation is a good resource.
+and Python 3. If you aren't, read :ref:`Python's official porting guide
+<pyporting-howto>` first. Refreshing your knowledge of unicode handling on
+Python 2 and 3 will help; the `Pragmatic Unicode`_ presentation is a good
+resource.
Django uses the *Python 2/3 Compatible Source* strategy. Of course, you're
free to chose another strategy for your own code, especially if you don't need
@@ -42,7 +43,6 @@ developers are used to dealing with such constraints.
Porting tools provided by Django are inspired by this philosophy, and it's
reflected throughout this guide.
-.. _Python's official porting guide: https://docs.python.org/3/howto/pyporting.html
.. _Pragmatic Unicode: http://nedbatchelder.com/text/unipain.html
Porting tips