[Python-checkins] peps: More backticks.

[eric.smith]

http://hg.python.org/peps/rev/2e29a596f460
changeset:   4288:2e29a596f460
user:        Eric V. Smith <eric at trueblade.com>
date:        Fri Apr 20 08:35:55 2012 -0400
summary:
  More backticks.

files:
  pep-0420.txt |  12 ++++++------
  1 files changed, 6 insertions(+), 6 deletions(-)


diff --git a/pep-0420.txt b/pep-0420.txt
--- a/pep-0420.txt
+++ b/pep-0420.txt
@@ -55,9 +55,9 @@
 invoked independent of which portion of the package gets imported
 first. As a consequence, the package's ``__init__.py`` cannot
 practically define any names as it depends on the order of the package
-fragments on sys.path which portion is imported first. As a special
-feature, ``extend_path`` reads files named ``<packagename>.pkg`` which
-allow to declare additional portions.
+fragments on ``sys.path`` which portion is imported first. As a
+special feature, ``extend_path`` reads files named
+``<packagename>.pkg`` which allow to declare additional portions.
 
 setuptools provides a similar function named
 ``pkg_resources.declare_namespace`` that is used in the form::
@@ -87,9 +87,9 @@
 whereas pkgutil doesn't.
 
 Namespace packages are designed to support being split across multiple
-directories (and hence found via multiple sys.path entries).  In this
-configuration, it doesn't matter if multiple portions all provide an
-``__init__.py`` file, so long as each portion correctly initializes
+directories (and hence found via multiple ``sys.path`` entries).  In
+this configuration, it doesn't matter if multiple portions all provide
+an ``__init__.py`` file, so long as each portion correctly initializes
 the namespace package. However, Linux distribution vendors (amongst
 others) prefer to combine the separate portions and install them all
 into the *same* filesystem directory. This creates a potential for

-- 
Repository URL: http://hg.python.org/peps