summaryrefslogtreecommitdiffstats
path: root/Tools/freeze
diff options
context:
space:
mode:
Diffstat (limited to 'Tools/freeze')
-rw-r--r--Tools/freeze/checkextensions_win32.py4
-rw-r--r--Tools/freeze/makefreeze.py2
2 files changed, 3 insertions, 3 deletions
diff --git a/Tools/freeze/checkextensions_win32.py b/Tools/freeze/checkextensions_win32.py
index a41542f..ee446e7 100644
--- a/Tools/freeze/checkextensions_win32.py
+++ b/Tools/freeze/checkextensions_win32.py
@@ -3,7 +3,7 @@
Under Windows it is unlikely the .obj files are of use, as special compiler options
are needed (primarily to toggle the behavior of "public" symbols.
-I dont consider it worth parsing the MSVC makefiles for compiler options. Even if
+I don't consider it worth parsing the MSVC makefiles for compiler options. Even if
we get it just right, a specific freeze application may have specific compiler
options anyway (eg, to enable or disable specific functionality)
@@ -14,7 +14,7 @@ So my basic strategy is:
your own).
* This description can include:
- The MSVC .dsp file for the extension. The .c source file names
- are extraced from there.
+ are extracted from there.
- Specific compiler/linker options
- Flag to indicate if Unicode compilation is expected.
diff --git a/Tools/freeze/makefreeze.py b/Tools/freeze/makefreeze.py
index 4cd1e96..ef18ec7 100644
--- a/Tools/freeze/makefreeze.py
+++ b/Tools/freeze/makefreeze.py
@@ -61,7 +61,7 @@ def makefreeze(base, dict, debug=0, entry_point=None, fail_import=()):
outfp.write('\t{"%s", M_%s, %d},\n' % (mod, mangled, size))
outfp.write('\n')
# The following modules have a NULL code pointer, indicating
- # that the prozen program should not search for them on the host
+ # that the frozen program should not search for them on the host
# system. Importing them will *always* raise an ImportError.
# The zero value size is never used.
for mod in fail_import: