[Python-checkins] r75361 - in sandbox/trunk/faq: design.rst extending.rst general.rst gui.rst programming.rst
georg.brandl
python-checkins at python.org
Sun Oct 11 20:17:31 CEST 2009
Author: georg.brandl
Date: Sun Oct 11 20:17:31 2009
New Revision: 75361
Log:
Fix remaining links that either are now internal or now must be external.
Modified:
sandbox/trunk/faq/design.rst
sandbox/trunk/faq/extending.rst
sandbox/trunk/faq/general.rst
sandbox/trunk/faq/gui.rst
sandbox/trunk/faq/programming.rst
Modified: sandbox/trunk/faq/design.rst
==============================================================================
--- sandbox/trunk/faq/design.rst (original)
+++ sandbox/trunk/faq/design.rst Sun Oct 11 20:17:31 2009
@@ -91,9 +91,8 @@
if expected_result-epsilon <= computation() <= expected_result+epsilon:
...
-Please see the chapter on `floating point arithmetic
-<http://docs.python.org/tutorial/floatingpoint>`_ in the Python tutorial for
-more information.
+Please see the chapter on :ref:`floating point arithmetic <tut-fp-issues>` in
+the Python tutorial for more information.
Why are Python strings immutable?
@@ -322,9 +321,8 @@
You can do this easily enough with a sequence of ``if... elif... elif... else``.
There have been some proposals for switch statement syntax, but there is no
-consensus (yet) on whether and how to do range tests. See `PEP 275
-<http://python.org/dev/peps/pep-0275/>`_ for complete details and the current
-status.
+consensus (yet) on whether and how to do range tests. See :pep:`275` for
+complete details and the current status.
For cases where you need to choose from a very large number of possibilities,
you can create a dictionary mapping case values to functions to call. For
@@ -398,12 +396,12 @@
``x+1``.
Several projects described in the Python newsgroup or at past `Python
-conferences </community/workshops/>`_ have shown that this approach is feasible,
+conferences <http://python.org/community/workshops/>`_ have shown that this approach is feasible,
although the speedups reached so far are only modest (e.g. 2x). Jython uses the
same strategy for compiling to Java bytecode. (Jim Hugunin has demonstrated
that in combination with whole-program analysis, speedups of 1000x are feasible
for small demo programs. See the proceedings from the `1997 Python conference
-</community/workshops/1997-10/proceedings/>`_ for more information.)
+<http://python.org/community/workshops/1997-10/proceedings/>`_ for more information.)
Internally, Python source code is always translated into a bytecode
representation, and this bytecode is then executed by the Python virtual
Modified: sandbox/trunk/faq/extending.rst
==============================================================================
--- sandbox/trunk/faq/extending.rst (original)
+++ sandbox/trunk/faq/extending.rst Sun Oct 11 20:17:31 2009
@@ -11,8 +11,8 @@
-----------------------------------
Yes, you can create built-in modules containing functions, variables, exceptions
-and even new types in C. This is explained in the document "Extending and
-Embedding the Python Interpreter" (http://docs.python.org/ext/ext.html).
+and even new types in C. This is explained in the document
+:ref:`extending-index`.
Most intermediate or advanced Python books will also cover this topic.
Modified: sandbox/trunk/faq/general.rst
==============================================================================
--- sandbox/trunk/faq/general.rst (original)
+++ sandbox/trunk/faq/general.rst Sun Oct 11 20:17:31 2009
@@ -50,8 +50,8 @@
unmodified), or to sell products that incorporate Python in some form. We would
still like to know about all commercial use of Python, of course.
-See `the PSF license page </psf/license/>`_ to find further explanations and a
-link to the full text of the license.
+See `the PSF license page <http://python.org/psf/license/>`_ to find further
+explanations and a link to the full text of the license.
The Python logo is trademarked, and in certain cases permission is required to
use it. Consult `the Trademark Usage Policy
@@ -124,8 +124,8 @@
Python versions are numbered A.B.C or A.B. A is the major version number -- it
is only incremented for really major changes in the language. B is the minor
version number, incremented for less earth-shattering changes. C is the
-micro-level -- it is incremented for each bugfix release. See `PEP 6
-</dev/peps/pep-0006/>`_ for more information about bugfix releases.
+micro-level -- it is incremented for each bugfix release. See :pep:`6` for more
+information about bugfix releases.
Not all releases are bugfix releases. In the run-up to a new major release, a
series of development releases are made, denoted as alpha, beta, or release
@@ -239,7 +239,7 @@
.. XXX adapt link to dev guide
For more information on how Python is developed, consult `the Python Developer's
-Guide </dev/>`_.
+Guide <http://python.org/dev/>`_.
Are there any published articles about Python that I can reference?
@@ -306,11 +306,13 @@
guaranteed that interfaces will remain the same throughout a series of bugfix
releases.
-The `2.6.2 release </download/>`_ is recommended production-ready version at
-this point in time. Python 3.1 is also considered production-ready, but may be
-less useful, since currently there is more third party software available for
-Python 2 than for Python 3. Python 2 code will generally not run unchanged in
-Python 3.
+.. XXX this gets out of date pretty often
+
+The `2.6.4 release <http://python.org/download/>`_ is recommended
+production-ready version at this point in time. Python 3.1 is also considered
+production-ready, but may be less useful, since currently there is more third
+party software available for Python 2 than for Python 3. Python 2 code will
+generally not run unchanged in Python 3.
How many people are using Python?
@@ -367,9 +369,8 @@
all at a single stroke.
Providing a gradual upgrade path is necessary if a feature has to be changed.
-`PEP 5 <http://python.org/dev/peps/pep-0005/>`_ describes the procedure followed
-for introducing backward-incompatible changes while minimizing disruption for
-users.
+:pep:`5` describes the procedure followed for introducing backward-incompatible
+changes while minimizing disruption for users.
Is Python Y2K (Year 2000) Compliant?
Modified: sandbox/trunk/faq/gui.rst
==============================================================================
--- sandbox/trunk/faq/gui.rst (original)
+++ sandbox/trunk/faq/gui.rst Sun Oct 11 20:17:31 2009
@@ -89,9 +89,9 @@
can use MacOS X's Cocoa libraries. See the documentation that comes with the Mac
port.
-`Pythonwin <http://python.org/doc/windows/>`_ by Mark Hammond includes an
-interface to the Microsoft Foundation Classes and a Python programming
-environment using it that's written mostly in Python.
+:ref:`Pythonwin <windows-faq>` by Mark Hammond includes an interface to the
+Microsoft Foundation Classes and a Python programming environment using it
+that's written mostly in Python.
Tkinter questions
Modified: sandbox/trunk/faq/programming.rst
==============================================================================
--- sandbox/trunk/faq/programming.rst (original)
+++ sandbox/trunk/faq/programming.rst Sun Oct 11 20:17:31 2009
@@ -710,11 +710,11 @@
search of the standard library found remarkably few places where using an
if-then-else expression would make the code more understandable.
-In 2002, `PEP 308 </dev/peps/pep-0308>`_ was written proposing several possible
-syntaxes and the community was asked to vote on the issue. The vote was
-inconclusive. Most people liked one of the syntaxes, but also hated other
-syntaxes; many votes implied that people preferred no ternary operator rather
-than having a syntax they hated.
+In 2002, :pep:`308` was written proposing several possible syntaxes and the
+community was asked to vote on the issue. The vote was inconclusive. Most
+people liked one of the syntaxes, but also hated other syntaxes; many votes
+implied that people preferred no ternary operator rather than having a syntax
+they hated.
Is it possible to write obfuscated one-liners in Python?
More information about the Python-checkins
mailing list