summaryrefslogtreecommitdiffstats
path: root/Tools/freeze
diff options
context:
space:
mode:
authorEzio Melotti <ezio.melotti@gmail.com>2011-03-16 09:05:33 (GMT)
committerEzio Melotti <ezio.melotti@gmail.com>2011-03-16 09:05:33 (GMT)
commit13925008dc11f2a235627dc8c0440c0ce99171d9 (patch)
tree4746c36be25417c56cf86591bf222af49b7afdfd /Tools/freeze
parente3d09ff269330bd0076e3ab9cb81907fad717a68 (diff)
downloadcpython-13925008dc11f2a235627dc8c0440c0ce99171d9.zip
cpython-13925008dc11f2a235627dc8c0440c0ce99171d9.tar.gz
cpython-13925008dc11f2a235627dc8c0440c0ce99171d9.tar.bz2
#11565: Fix several typos. Patch by Piotr Kasprzyk.
Diffstat (limited to 'Tools/freeze')
-rw-r--r--Tools/freeze/checkextensions_win32.py2
1 files changed, 1 insertions, 1 deletions
diff --git a/Tools/freeze/checkextensions_win32.py b/Tools/freeze/checkextensions_win32.py
index ba3853c..a41542f 100644
--- a/Tools/freeze/checkextensions_win32.py
+++ b/Tools/freeze/checkextensions_win32.py
@@ -7,7 +7,7 @@ I dont consider it worth parsing the MSVC makefiles for compiler options. Even
we get it just right, a specific freeze application may have specific compiler
options anyway (eg, to enable or disable specific functionality)
-So my basic stragtegy is:
+So my basic strategy is:
* Have some Windows INI files which "describe" one or more extension modules.
(Freeze comes with a default one for all known modules - but you can specify