[Python-checkins] cpython (2.7): Issue #28820: Fix spelling of “practice” as a noun

martin.panter python-checkins at python.org
Wed Nov 30 05:21:11 EST 2016


https://hg.python.org/cpython/rev/4f24641cd030
changeset:   105397:4f24641cd030
branch:      2.7
user:        Martin Panter <vadmium+py at gmail.com>
date:        Wed Nov 30 10:18:45 2016 +0000
summary:
  Issue #28820: Fix spelling of “practice” as a noun

files:
  Doc/howto/urllib2.rst          |  2 +-
  Doc/tutorial/modules.rst       |  2 +-
  Mac/Modules/cg/CFMLateImport.c |  2 +-
  3 files changed, 3 insertions(+), 3 deletions(-)


diff --git a/Doc/howto/urllib2.rst b/Doc/howto/urllib2.rst
--- a/Doc/howto/urllib2.rst
+++ b/Doc/howto/urllib2.rst
@@ -567,7 +567,7 @@
 .. [#] For an introduction to the CGI protocol see
        `Writing Web Applications in Python <http://www.pyzine.com/Issue008/Section_Articles/article_CGIOne.html>`_.
 .. [#] Google for example.
-.. [#] Browser sniffing is a very bad practise for website design - building
+.. [#] Browser sniffing is a very bad practice for website design - building
        sites using web standards is much more sensible. Unfortunately a lot of
        sites still send different versions to different browsers.
 .. [#] The user agent for MSIE 6 is
diff --git a/Doc/tutorial/modules.rst b/Doc/tutorial/modules.rst
--- a/Doc/tutorial/modules.rst
+++ b/Doc/tutorial/modules.rst
@@ -496,7 +496,7 @@
 ``__all__`` is defined.)
 
 Although certain modules are designed to export only names that follow certain
-patterns when you use ``import *``, it is still considered bad practise in
+patterns when you use ``import *``, it is still considered bad practice in
 production code.
 
 Remember, there is nothing wrong with using ``from Package import
diff --git a/Mac/Modules/cg/CFMLateImport.c b/Mac/Modules/cg/CFMLateImport.c
--- a/Mac/Modules/cg/CFMLateImport.c
+++ b/Mac/Modules/cg/CFMLateImport.c
@@ -894,7 +894,7 @@
     MoreAssertQ(fragToFix->sectionHeaders != nil);
     MoreAssertQ(fragToFix->loaderSection != nil);
     MoreAssertQ(fragToFix->section0Base != nil);        // Technically, having a nil for these two is not a problem, ...
-    MoreAssertQ(fragToFix->section1Base != nil);        // but in practise it a wildly deviant case and we should know about it.
+    MoreAssertQ(fragToFix->section1Base != nil);        // but in practice it a wildly deviant case and we should know about it.
     MoreAssertQ(importLibrary != nil);
     MoreAssertQ(lookup != nil);
 

-- 
Repository URL: https://hg.python.org/cpython


More information about the Python-checkins mailing list