remove trailing whitespace

Author: John-Colvin

README.md

@@ -1,32 +1,32 @@
-[![build-status-badge]][build-status]
-[![docs-badge]][docs]
-[![pypi-version]][pypi]
-[![license-badge]][license]
-
-# PyD
-
-PyD provides seamless interoperability between Python and the D programming language.
-
-# Requirements
-
-## Python
-
-CPython 2.6+
-
-## D Compilers
-
-* DMD, LDC fe2.065+
-* GDC fe2.065+, embedding only (GDC still doesn't have shared library support!)
-
-Note all D compilers are based on DMD's front end, so while LDC and GDC have 
-their own verisoning schemes, I only pay attention to the front end version. 
-
-
-[build-status-badge]: https://travis-ci.org/ariovistus/pyd.svg?branch=master
-[build-status]: https://travis-ci.org/ariovistus/pyd
-[docs-badge]: https://readthedocs.org/projects/pyd/badge/
-[docs]: http://pyd.readthedocs.org/
-[pypi-version]: https://pypip.in/version/pyd/badge.svg
-[pypi]: https://pypi.python.org/pypi/pyd
-[license-badge]: https://pypip.in/license/pyd/badge.svg
-[license]: https://pypi.python.org/pypi/pyd/
+[![build-status-badge]][build-status]
+[![docs-badge]][docs]
+[![pypi-version]][pypi]
+[![license-badge]][license]
+
+# PyD
+
+PyD provides seamless interoperability between Python and the D programming language.
+
+# Requirements
+
+## Python
+
+CPython 2.6+
+
+## D Compilers
+
+* DMD, LDC fe2.065+
+* GDC fe2.065+, embedding only (GDC still doesn't have shared library support!)
+
+Note all D compilers are based on DMD's front end, so while LDC and GDC have
+their own verisoning schemes, I only pay attention to the front end version.
+
+
+[build-status-badge]: https://travis-ci.org/ariovistus/pyd.svg?branch=master
+[build-status]: https://travis-ci.org/ariovistus/pyd
+[docs-badge]: https://readthedocs.org/projects/pyd/badge/
+[docs]: http://pyd.readthedocs.org/
+[pypi-version]: https://pypip.in/version/pyd/badge.svg
+[pypi]: https://pypi.python.org/pypi/pyd
+[license-badge]: https://pypip.in/license/pyd/badge.svg
+[license]: https://pypi.python.org/pypi/pyd/

credits.txt

@@ -1,8 +1,8 @@
-Python/D bindings:
-Deja Augustine, David Rushby, Kirk McDonald
-
-CeleriD:
-David Rushby, Kirk McDonald
-
-Pyd:
-Kirk McDonald
+Python/D bindings:
+Deja Augustine, David Rushby, Kirk McDonald
+
+CeleriD:
+David Rushby, Kirk McDonald
+
+Pyd:
+Kirk McDonald

docs/deimos_modules.ddoc

@@ -1,4 +1,4 @@
-MODULES = 
+MODULES =
 	$(MODULE deimos.python.abstract_)
 	$(MODULE deimos.python.ast)
 	$(MODULE deimos.python.boolobject)

docs/modules.ddoc

@@ -1,4 +1,4 @@
-MODULES = 
+MODULES =
 	$(MODULE pyd.class_wrap)
 	$(MODULE pyd.def)
 	$(MODULE pyd.embedded)

docs/source/authors.rst

@@ -1,4 +1,4 @@
-Authors 
+Authors
 =======
 
 PyD was originally written by Kirk McDonald.
@@ -9,7 +9,7 @@ Other contributors:
  * Deja Augustine
  * Don Clugston
  * Ellery Newcomer
- 
+
 Special thanks to Tomasz Stachowiak and Daniel Keep for providing now-defunct metaprogramming modules which were vital to the early development of Pyd.
 
 

docs/source/classes.rst

@@ -1,7 +1,7 @@
 Exposing D classes to python
 ============================
 
-The heart of PyD's class wrapping features is the `class_wrap` 
+The heart of PyD's class wrapping features is the `class_wrap`
 function template.
 
 Member wrapping
@@ -70,7 +70,7 @@ Specify whether property is read-only, write-only, or read-write.
 
 Possible values: :code:`"r"`, :code:`"w"`, :code:`"rw"`, :code:`""`
 
-When :code:`""`, determine mode based on availability of getter and setter 
+When :code:`""`, determine mode based on availability of getter and setter
 forms.
 
 Default: :code:`""`
@@ -105,29 +105,29 @@ Operator
 Notes on wrapped operators
     * only one overload is permitted per operator; however OpBinary and OpBinaryRight may "share" an operator.
     * PyD only supports opSlice, opSliceAssign if both of their two indices are
-      implicitly convertable to Py_ssize_t. This is a limitation of the 
-      Python/C API. Note this means the zero-argument form of opSlice 
+      implicitly convertable to Py_ssize_t. This is a limitation of the
+      Python/C API. Note this means the zero-argument form of opSlice
       (:code:`foo[]`) cannot be wrapped.
-    * :code:`~`, :code:`~=`: Python does not have a dedicated array 
-      concatenation operator. 
-      :code:`+` is reused for this purpose. Therefore, odd behavior may result 
+    * :code:`~`, :code:`~=`: Python does not have a dedicated array
+      concatenation operator.
+      :code:`+` is reused for this purpose. Therefore, odd behavior may result
       with classes that overload both :code:`+` and :code:`~`. The Python/C API
-      does consider addition and concantenation to be distinct operations, 
+      does consider addition and concantenation to be distinct operations,
       though.
-    * :code:`in`: Semantics vary slightly. In python, :code:`in` is a 
-      containment test and retursn a bool. In D, by convention 
+    * :code:`in`: Semantics vary slightly. In python, :code:`in` is a
+      containment test and retursn a bool. In D, by convention
       :code:`in` is a lookup, returning a pointer or null. PyD will check the
       boolean result of a call to the overload and return that value to Python.
 
 
 Iterator wrapping
 -----------------
 
-A wrapped class can be make iterable in python by supplying defs with the 
+A wrapped class can be make iterable in python by supplying defs with the
 python names:
 
     * :code:`__iter__`, which should return :code:`this`.
-    * :code:`next`, which should return the next item, or null to signal 
+    * :code:`next`, which should return the next item, or null to signal
       termination. Signature must be :code:`PyObject* next()`.
 
 Alternatively, you can supply a single :code:`__iter__` that returns a Range.

docs/source/conversion.rst

@@ -1,7 +1,7 @@
 Type Conversion
 ===============
 
-PyD provides `d_to_python` and `python_to_d` for converting types to and from 
+PyD provides `d_to_python` and `python_to_d` for converting types to and from
 python. These functions almost always do a copy. If you want reference semantics, use `PydObject`.
 
 D to Python
@@ -51,7 +51,7 @@ complex                         std.complex.Complex
 float                           float, double, real
 int, long                       Any integral type
 bool                            bool
-buffer                          dynamic or static array (with many dimensions!) 
+buffer                          dynamic or static array (with many dimensions!)
 datetime.date                   std.datetime.Date, std.datetime.DateTime, std.datetime.SysTime
 datetime.datetime               std.datetime.Date, std.datetime.DateTime, std.datetime.SysTime, std.datetime.Time
 datetime.time                   std.datetime.Time
@@ -79,11 +79,11 @@ class or struct.
 results:
 
 .. code-block:: python
-    
+
     example.foo()
     example.bar(20)
 
 .. code-block:: bash
-    
+
     12
     S(20)

docs/source/distutils.rst

@@ -4,7 +4,7 @@ PyD and distutils
 PyD provides patches to distutils so it can use DMD, LDC, and GDC.
 
 .. seealso::
-    
+
     `distutils <https://docs.python.org/2/library/distutils.html#module-distutils>`__
 
 
@@ -64,26 +64,26 @@ Default: :code:`False`
 
 with_pyd
 --------
-Setting this flag to :code:`False` suppresses compilation and linkage of PyD. 
-`with_main` effectively becomes :code:`False` as well; `PydMain` won't be used 
+Setting this flag to :code:`False` suppresses compilation and linkage of PyD.
+`with_main` effectively becomes :code:`False` as well; `PydMain` won't be used
 unless PyD is in use.
 
 Default: :code:`True`
 
 with_main
 ---------
-Setting this flag to :code:`False` suppresses the use of `PydMain`, allowing 
+Setting this flag to :code:`False` suppresses the use of `PydMain`, allowing
 the user to write a C-style init function instead.
 
 Default: :code:`True`
 
 build_deimos
 ------------
-Build object files for deimos headers. Ideally, this should not be necessary; 
-however some compilers (\*cough* ldc) try to link to PyObject typeinfo. If you 
-get link errors like 
+Build object files for deimos headers. Ideally, this should not be necessary;
+however some compilers (\*cough* ldc) try to link to PyObject typeinfo. If you
+get link errors like
 
-`undefined symbol: _D6deimos6python12methodobject11PyMethodDef6__initZ` 
+`undefined symbol: _D6deimos6python12methodobject11PyMethodDef6__initZ`
 
 try setting this flag to :code:`True`.
 
@@ -112,24 +112,24 @@ Default: :code:`False`
 d_property
 ----------
 
-Have D compilers enable property checks (i.e. trying to call functions without 
+Have D compilers enable property checks (i.e. trying to call functions without
 parens will result in an error)
 
 Default: :code:`False`
 
 string_imports
 --------------
 
-Specify string import files to pass to D compilers. Takes a list of strings 
-which are either paths to import files or paths to directories containing 
+Specify string import files to pass to D compilers. Takes a list of strings
+which are either paths to import files or paths to directories containing
 import files.
 
 Default: :code:`[]`
 
 
 pydexe
 ~~~~~~
-PyD also provides a custom command to compile D code that embeds python. The 
+PyD also provides a custom command to compile D code that embeds python. The
 format of setup.py stays the same.
 
 .. literalinclude:: ../../examples/pyind/setup.py

docs/source/embed.rst

@@ -14,7 +14,7 @@ Some Notes:
 Once again, we use distutils to compile this code using the special command `pydexe`:
 
 .. literalinclude:: ../../examples/simple_embedded/setup.py
-    
+
 .. code-block:: bash
 
     $ python setup.py install
@@ -36,11 +36,11 @@ call stack is not deep enough
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 Certain python modules (i.e. :code:`inspect`) expect python to have a nonempty
-call stack. This seems not to be the case in embedded python. To work around 
+call stack. This seems not to be the case in embedded python. To work around
 this, use :code:`InterpContext.pushDummyFrame`:
 
 .. code-block:: d
-    
+
     context.pushDummyFrame();
     py_stmts("import inspect");
     context.popDummyFrame();

docs/source/exception.rst

@@ -5,19 +5,19 @@ The raw Python/C API has a protocol for allowing C extensions to use Python's ex
 
 
 :code:`handle_exception`
------------------------- 
-check if a Python exception has been set, and if it has, throw a 
+------------------------
+check if a Python exception has been set, and if it has, throw a
 :code:`PythonException`. Clear the Python error code.
 
 :code:`exception_catcher`
-------------------------- 
-wrap a D delegate and set a Python error code if a D exception occurs. 
-Returns a python-respected "invalid" value (null or -1), or the result of 
+-------------------------
+wrap a D delegate and set a Python error code if a D exception occurs.
+Returns a python-respected "invalid" value (null or -1), or the result of
 the delegate if nothing was thrown.
 
 Notes
-    * If your code interfaces with python directly, you should probably 
+    * If your code interfaces with python directly, you should probably
       wrap it with :code:`exception_catcher` (uncaught D exceptions will crash
       the python interpreter).
-    * All wrapped functions, methods, constructors, etc, handle D and 
+    * All wrapped functions, methods, constructors, etc, handle D and
       python exceptions already.

docs/source/extend.rst

@@ -24,7 +24,7 @@ This extension is then built the usual way with distutils, except PyD provides s
 
     $ python setup.py install
 
-Usage: 
+Usage:
 
 .. code-block:: python
 

docs/source/functions.rst

@@ -54,7 +54,7 @@ specify the module in which to inject the function
 
 Default: `''`
 
-.. _Docstring: 
+.. _Docstring:
 
 Docstring
 ---------
@@ -63,7 +63,7 @@ Specify the docstring to associate with the function
 
 Default: :code:`''`
 
-.. _PyName: 
+.. _PyName:
 
 PyName
 ------

docs/source/pydobject.rst

@@ -7,11 +7,11 @@ PydObject wraps a PyObject*. It handles the python reference count for you, and
     :language: d
 
 Notes:
-    * Due to some residual awkwardness with D's properties, member functions 
-      with zero or one arguments must be accessed through `method`, 
+    * Due to some residual awkwardness with D's properties, member functions
+      with zero or one arguments must be accessed through `method`,
       `method_unpack`, etc. Member functions with two or more arguments can be
       called directly.
-    * Calling a member function will result in another PydObject; call 
+    * Calling a member function will result in another PydObject; call
       :code:`to_d!T()` to convert it to a D object.
     * PydObjects are callable
     * PydObjects are iterable
@@ -20,6 +20,6 @@ Notes:
 Buffer protocol
 ---------------
 
-PydObject exposes a near-raw interface to the buffer protocol which can be 
-used to e.g. read values from a numpy array without copying the entire thing 
+PydObject exposes a near-raw interface to the buffer protocol which can be
+used to e.g. read values from a numpy array without copying the entire thing
 into a D data structure.