Misc typos

Found via `codespell`

Cython/Compiler/Buffer.py

@@ -370,7 +370,7 @@ def put_assign_to_buffer(lhs_cname, rhs_cname, buf_entry,
     pybuffernd_struct = buffer_aux.buflocal_nd_var.cname
     flags = get_flags(buffer_aux, buffer_type)
 
-    code.putln("{")  # Set up necesarry stack for getbuffer
+    code.putln("{")  # Set up necessary stack for getbuffer
     code.putln("__Pyx_BufFmt_StackElem __pyx_stack[%d];" % buffer_type.dtype.struct_nesting_depth())
 
     getbuffer = get_getbuffer_call(code, "%s", buffer_aux, buffer_type) # fill in object below

Cython/Compiler/Code.py

@@ -440,7 +440,7 @@ class UtilityCode(UtilityCodeBase):
     hashes/equals by instance
 
     proto           C prototypes
-    impl            implemenation code
+    impl            implementation code
     init            code to call on module initialization
     requires        utility code dependencies
     proto_block     the place in the resulting file where the prototype should
@@ -1639,7 +1639,7 @@ class CCodeWriter(object):
       as well
     - labels, temps, exc_vars: One must construct a scope in which these can
       exist by calling enter_cfunc_scope/exit_cfunc_scope (these are for
-      sanity checking and forward compatabilty). Created insertion points
+      sanity checking and forward compatibility). Created insertion points
       looses this scope and cannot access it.
     - marker: Not copied to insertion point
     - filename_table, filename_list, input_file_contents: All codewriters

Cython/Compiler/CythonScope.py

@@ -27,7 +27,7 @@ class CythonScope(ModuleScope):
             entry.in_cinclude = True
 
     def is_cpp(self):
-        # Alow C++ utility code in C++ contexts.
+        # Allow C++ utility code in C++ contexts.
         return self.context.cpp
 
     def lookup_type(self, name):

Cython/Compiler/FusedNode.py

@@ -276,7 +276,7 @@ class FusedCFuncDefNode(StatListNode):
 
     def _fused_instance_checks(self, normal_types, pyx_code, env):
         """
-        Genereate Cython code for instance checks, matching an object to
+        Generate Cython code for instance checks, matching an object to
         specialized types.
         """
         for specialized_type in normal_types:

Cython/Compiler/Main.py

@@ -509,7 +509,7 @@ def run_pipeline(source, options, full_module_name=None, context=None):
 
 class CompilationSource(object):
     """
-    Contains the data necesarry to start up a compilation pipeline for
+    Contains the data necessary to start up a compilation pipeline for
     a single compilation unit.
     """
     def __init__(self, source_desc, full_module_name, cwd):

Cython/Compiler/Nodes.py

@@ -1942,7 +1942,7 @@ class FuncDefNode(StatNode, BlockNode):
                     code.put_var_incref(entry)
 
             # Note: defaults are always incref-ed. For def functions, we
-            #       we acquire arguments from object converstion, so we have
+            #       we acquire arguments from object conversion, so we have
             #       new references. If we are a cdef function, we need to
             #       incref our arguments
             elif is_cdef and entry.type.is_memoryviewslice and len(entry.cf_assignments) > 1:

Cython/Compiler/Symtab.py

@@ -122,7 +122,7 @@ class Entry(object):
     #
     # buffer_aux       BufferAux or None  Extra information needed for buffer variables
     # inline_func_in_pxd boolean  Hacky special case for inline function in pxd file.
-    #                             Ideally this should not be necesarry.
+    #                             Ideally this should not be necessary.
     # might_overflow   boolean    In an arithmetic expression that could cause
     #                             overflow (used for type inference).
     # utility_code_definition     For some Cython builtins, the utility code
@@ -2421,7 +2421,7 @@ class CppClassScope(Scope):
         # to work with this type.
         for base_entry in \
             base_scope.inherited_var_entries + base_scope.var_entries:
-                #contructor/destructor is not inherited
+                #constructor/destructor is not inherited
                 if base_entry.name in ("<init>", "<del>"):
                     continue
                 #print base_entry.name, self.entries

Cython/Compiler/TypeInference.py

@@ -378,7 +378,7 @@ class SimpleAssignmentTypeInferer(object):
                     self.set_entry_type(entry, py_object_type)
             return
 
-        # Set of assignemnts
+        # Set of assignments
         assignments = set()
         assmts_resolved = set()
         dependencies = {}

Cython/Debugger/libcython.py

@@ -488,7 +488,7 @@ class SourceFileDescriptor(object):
 
 class CyGDBError(gdb.GdbError):
     """
-    Base class for Cython-command related erorrs
+    Base class for Cython-command related errors
     """
 
     def __init__(self, *args):

docs/src/userguide/memoryviews.rst

@@ -352,7 +352,7 @@ For a 3D C contiguous array::
     Out[6]: (12, 4, 1)
 
 A Fortran contiguous array has the opposite memory ordering, with the elements
-on the first axis closest togther in memory::
+on the first axis closest together in memory::
 
     In [7]: f_contig = np.array(c_contig, order='F')
     In [8]: np.all(f_contig == c_contig)

pyximport/pyximport.py

@@ -82,7 +82,7 @@ def _info(message, *args):
 # already built. It might be more efficient to only do it when the
 # mod time of the .pyx is newer than the mod time of the .so but
 # the question is how to get distutils to tell me the name of the .so
-# before it builds it. Maybe it is easy...but maybe the peformance
+# before it builds it. Maybe it is easy...but maybe the performance
 # issue isn't real.
 def _load_pyrex(name, filename):
     "Load a pyrex file given a name and filename."

tests/errors/e_directives.pyx

 # mode: error
 
-# cython: nonexistant = True
+# cython: nonexistent = True
 # cython: boundscheck = true
 # cython: boundscheck = 9