A few README tweaks (#73) (#80)

* Add a paragraph at the top for users, not builders, of Python.

* Use nicer rst url syntax to avoid borking paragraphs in the plain text.

Contributed by Ned Batchelder @nedbat

(cherry picked from commit 3cdbd68ce8230cff1afb67472b96fbfa7f047e32)

diff --git a/README b/README
index de3a091e07a598d102c063a168371d907662f5c9..8133b3191689ef42018ebfd3c102ed3c70ec4afd 100644 (file)
--- a/README
+++ b/README
@@ -11,6 +11,14 @@ especially how built-in objects like dictionaries and strings work,
 have changed considerably, and a lot of deprecated features have finally
 been removed.
 
+Using Python
+------------
+
+Installable Python kits, and information about using Python, are available at
+`python.org`_.
+
+.. _python.org: https://www.python.org/
+
 
 Build Instructions
 ------------------
@@ -151,7 +159,7 @@ IMPORTANT: If the tests fail and you decide to mail a bug report, *don't*
 include the output of "make test".  It is useless.  Run the failing test
 manually, as follows:
 
-        ./python -m test -v test_whatever
+    ./python -m test -v test_whatever
 
 (substituting the top of the source tree for '.' if you built in a different
 directory).  This runs the test in verbose mode.
@@ -198,11 +206,12 @@ Proposals for enhancement
 -------------------------
 
 If you have a proposal to change Python, you may want to send an email to the
-comp.lang.python or python-ideas mailing lists for inital feedback.  A Python
+comp.lang.python or `python-ideas`_ mailing lists for initial feedback.  A Python
 Enhancement Proposal (PEP) may be submitted if your idea gains ground.  All
 current PEPs, as well as guidelines for submitting a new PEP, are listed at
 http://www.python.org/dev/peps/.
 
+.. _python-ideas: https://mail.python.org/mailman/listinfo/python-ideas/
 
 Release Schedule
 ----------------