From 449b3f74b7698a122382b8fea9a911ffd93c4719 Mon Sep 17 00:00:00 2001 From: "Eric V. Smith" Date: Wed, 23 May 2012 08:20:02 -0400 Subject: [PATCH] Improved wording. --- pep-0420.txt | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/pep-0420.txt b/pep-0420.txt index fff17d5a6..a0dbb6d35 100644 --- a/pep-0420.txt +++ b/pep-0420.txt @@ -409,10 +409,10 @@ In the same thread [8]_, it was pointed out that this restriction is not required. If the parent path is looked up by name instead of by holding a reference to it, then there is no restriction on how the parent path is modified or replaced. For a top-level namespace -package, the lookup would be a module ``"sys"`` then its attribute -``"path"``. For a namespace package nested inside a module ``foo``, -the lookup would be module ``"foo"`` then its attribute -``"__path__"``. +package, the lookup would be the module named ``"sys"`` then its +attribute ``"path"``. For a namespace package nested inside a package +``foo``, the lookup would be for the module named ``"foo"`` then its +attribute ``"__path__"``. Module reprs