Remove trailing whitespace

Author: mwtoews

DEPENDENCIES.txt

@@ -1,4 +1,4 @@
 - python 3.8+
 - setuptools
-- libspatialindex C library 1.8.5+: 
+- libspatialindex C library 1.8.5+:
   https://libspatialindex.org/

LICENSE.txt

@@ -1,6 +1,6 @@
 The MIT License (MIT)
 
-Copyright (c) 2018: Sean C. Gillies, Howard Butler and contributors 
+Copyright (c) 2018: Sean C. Gillies, Howard Butler and contributors
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

ci/CMakeLists.txt

@@ -23,7 +23,7 @@ mark_as_advanced(CMAKE_VERBOSE_MAKEFILE)
 set(CMAKE_MODULE_PATH "${PROJECT_SOURCE_DIR}/cmake/modules" ${CMAKE_MODULE_PATH})
 
 # Make string comparison in cmake behave like you'd expect
-cmake_policy(SET CMP0054 NEW) 
+cmake_policy(SET CMP0054 NEW)
 
 if (WIN32)
     if(${CMAKE_VERSION} VERSION_GREATER "3.14.5")
@@ -72,7 +72,7 @@ if(WIN32)
 	endif( CMAKE_SIZEOF_VOID_P EQUAL 8 )
       endif()
 endif()
- 
+
 set(CMAKE_INCLUDE_DIRECTORIES_PROJECT_BEFORE ON)
 
 include (CheckFunctionExists)

ci/install_libspatialindex.bat

@@ -2,7 +2,7 @@ python -c "import sys; print(sys.version)"
 
 set SIDX_VERSION=1.9.3
 
-curl -OL "https://github.com/libspatialindex/libspatialindex/archive/%SIDX_VERSION%.zip" 
+curl -OL "https://github.com/libspatialindex/libspatialindex/archive/%SIDX_VERSION%.zip"
 
 tar xvf "%SIDX_VERSION%.zip"
 

docs/source/class.txt

@@ -5,9 +5,9 @@ Class Documentation
 
 .. autoclass:: rtree.index.Index
     :members: __init__, insert, intersection, nearest, delete, bounds, count, close, dumps, loads
-    
+
 .. autoclass:: rtree.index.Property
-    :members: 
+    :members:
 
 .. autoclass:: rtree.index.Item
     :members:  __init__, bbox, object

docs/source/history.txt

@@ -24,11 +24,11 @@ of new features and much more flexibility. See :ref:`changes` for more detail.
 .. note::
     A significant bug in the 1.6.1+ `libspatialindex`_ C API was found where
     it was using unsigned integers for index entry IDs instead of signed
-    integers. Because `Rtree`_ appeared to be the only significant user of the 
-    C API at this time, it was corrected immediately.  You should update 
-    immediately and re-insert data into new indexes if this is an important 
+    integers. Because `Rtree`_ appeared to be the only significant user of the
+    C API at this time, it was corrected immediately.  You should update
+    immediately and re-insert data into new indexes if this is an important
     consideration for your application.
-    
+
 Rtree 0.5.0 included a C library that is now the C API for libspatialindex and
 is part of that source tree. The code bases are independent from each other
 and can now evolve separately. Rtree is pure Python as of 0.6.0+.

docs/source/index.txt

@@ -3,8 +3,8 @@
 Rtree: Spatial indexing for Python
 ------------------------------------------------------------------------------
 
-`Rtree`_ is a `ctypes`_ Python wrapper of `libspatialindex`_ that provides a 
-number of advanced spatial indexing features for the spatially curious Python 
+`Rtree`_ is a `ctypes`_ Python wrapper of `libspatialindex`_ that provides a
+number of advanced spatial indexing features for the spatially curious Python
 user.  These features include:
 
 * Nearest neighbor search
@@ -21,7 +21,7 @@ Documentation
 
 .. toctree::
    :maxdepth: 2
-   
+
    install
    tutorial
    class

docs/source/install.txt

@@ -3,7 +3,7 @@
 Installation
 ------------------------------------------------------------------------------
 
-\*nix 
+\*nix
 ..............................................................................
 
 First, download and install version 1.8.5+ of the `libspatialindex`_ library from:
@@ -14,8 +14,8 @@ The library is a GNU-style build, so it is a matter of::
 
   $ ./configure; make; make install
 
-You may need to run the ``ldconfig`` command after installing the library to 
-ensure that applications can find it at startup time.  
+You may need to run the ``ldconfig`` command after installing the library to
+ensure that applications can find it at startup time.
 
 At this point you can get Rtree 0.7.0 via easy_install::
 
@@ -29,11 +29,11 @@ You can build and test in place like::
 
   $ python setup.py test
 
-Windows 
+Windows
 ..............................................................................
 
-The Windows DLLs of `libspatialindex`_ are pre-compiled in 
-windows installers that are available from `PyPI`_.  Installation on Windows 
+The Windows DLLs of `libspatialindex`_ are pre-compiled in
+windows installers that are available from `PyPI`_.  Installation on Windows
 is as easy as::
 
   c:\python2x\scripts\easy_install.exe Rtree

docs/source/performance.txt

@@ -3,7 +3,7 @@
 Performance
 ------------------------------------------------------------------------------
 
-See the `tests/benchmarks.py`_ file for a comparison of various query methods 
+See the `tests/benchmarks.py`_ file for a comparison of various query methods
 and how much acceleration can be obtained from using Rtree.
 
 .. _tests/benchmarks.py: https://raw.github.com/Rtree/Rtree/master/tests/benchmarks.py
@@ -12,19 +12,19 @@ There are a few simple things that will improve performance.
 
 Use stream loading
 ..............................................................................
- 
+
 This will substantially (orders of magnitude in many cases) improve
 performance over :py:meth:`~rtree.index.Index.insert` by allowing the data to
-be pre-sorted   
+be pre-sorted
 
-:: 
+::
 
    >>> def generator_function(somedata):
    ...    for i, obj in enumerate(somedata):
    ...        yield (i, (obj.xmin, obj.ymin, obj.xmax, obj.ymax), obj)
    >>> r = index.Index(generator_function(somedata))
 
-After bulk loading the index, you can then insert additional records into 
+After bulk loading the index, you can then insert additional records into
 the index using :py:meth:`~rtree.index.Index.insert`
 
 Override :py:data:`~rtree.index.Index.dumps` to use the highest pickle protocol
@@ -42,7 +42,7 @@ Override :py:data:`~rtree.index.Index.dumps` to use the highest pickle protocol
 Use objects='raw'
 ...............................................................................
 
-In any :py:meth:`~rtree.index.Index.intersection` or 
+In any :py:meth:`~rtree.index.Index.intersection` or
 :py:meth:`~rtree.index.Index.nearest` or query, use objects='raw' keyword
 argument ::
 
@@ -61,7 +61,7 @@ Adjust :py:class:`rtree.index.Property` appropriate to your index.
    * Increase the :py:data:`~rtree.index.Property.fill_factor` to something
      near 0.9. Smaller fill factors mean more splitting, which means more
      nodes. This may be bad or good depending on your usage.
-   
+
 Limit dimensionality to the amount you need
 ...............................................................................
 
@@ -71,7 +71,7 @@ point comparisons for each query, search, and insert operation of the index.
 
 Use the correct query method
 ...............................................................................
- 
+
 Use :py:meth:`~rtree.index.Index.count` if you only need a count and
 :py:meth:`~rtree.index.Index.intersection` if you only need the ids.
 Otherwise, lots of data may potentially be copied.

docs/source/tutorial.txt

@@ -3,21 +3,21 @@
 Tutorial
 ------------------------------------------------------------------------------
 
-This tutorial demonstrates how to take advantage of :ref:`Rtree <home>` for 
-querying data that have a spatial component that can be modeled as bounding 
+This tutorial demonstrates how to take advantage of :ref:`Rtree <home>` for
+querying data that have a spatial component that can be modeled as bounding
 boxes.
 
 
 Creating an index
 ..............................................................................
 
-The following section describes the basic instantiation and usage of 
+The following section describes the basic instantiation and usage of
 :ref:`Rtree <home>`.
 
 Import
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-After :ref:`installing <installation>` :ref:`Rtree <home>`, you should be able to 
+After :ref:`installing <installation>` :ref:`Rtree <home>`, you should be able to
 open up a Python prompt and issue the following::
 
   >>> from rtree import index
@@ -30,21 +30,21 @@ with the index.
 Construct an instance
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-After importing the index module, construct an index with the default 
+After importing the index module, construct an index with the default
 construction::
 
   >>> idx = index.Index()
 
 .. note::
 
-    While the default construction is useful in many cases, if you want to 
-    manipulate how the index is constructed you will need pass in a 
-    :py:class:`rtree.index.Property` instance when creating the index. 
+    While the default construction is useful in many cases, if you want to
+    manipulate how the index is constructed you will need pass in a
+    :py:class:`rtree.index.Property` instance when creating the index.
 
 Create a bounding box
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-After instantiating the index, create a bounding box that we can 
+After instantiating the index, create a bounding box that we can
 insert into the index::
 
   >>> left, bottom, right, top = (0.0, 0.0, 1.0, 1.0)
@@ -67,16 +67,16 @@ Insert an entry into the index::
 
 .. note::
 
-    Entries that are inserted into the index are not unique in either the 
-    sense of the `id` or of the bounding box that is inserted with index 
-    entries. If you need to maintain uniqueness, you need to manage that before 
+    Entries that are inserted into the index are not unique in either the
+    sense of the `id` or of the bounding box that is inserted with index
+    entries. If you need to maintain uniqueness, you need to manage that before
     inserting entries into the Rtree.
 
 .. note::
 
     Inserting a point, i.e. where left == right && top == bottom, will
     essentially insert a single point entry into the index instead of copying
-    extra coordinates and inserting them. There is no shortcut to explicitly 
+    extra coordinates and inserting them. There is no shortcut to explicitly
     insert a single point, however.
 
 Query the index
@@ -95,7 +95,7 @@ Given a query window, return ids that are contained within the window::
   >>> list(idx.intersection((1.0, 1.0, 2.0, 2.0)))
   [0]
 
-Given a query window that is beyond the bounds of data we have in the 
+Given a query window that is beyond the bounds of data we have in the
 index::
 
   >>> list(idx.intersection((1.0000001, 1.0000001, 2.0, 2.0)))
@@ -106,7 +106,7 @@ Nearest Neighbors
 
 The following finds the 1 nearest item to the given bounds. If multiple items
 are of equal distance to the bounds, both are returned::
-  
+
   >>> idx.insert(1, (left, bottom, right, top))
   >>> list(idx.nearest((1.0000001, 1.0000001, 2.0, 2.0), 1))
   [0, 1]
@@ -138,10 +138,10 @@ to intersection::
 Serializing your index to a file
 ..............................................................................
 
-One of :ref:`Rtree <home>`'s most useful properties is the ability to 
-serialize Rtree indexes to disk. These include the clustered indexes 
+One of :ref:`Rtree <home>`'s most useful properties is the ability to
+serialize Rtree indexes to disk. These include the clustered indexes
 described :ref:`here <clustered>`::
-  
+
   >>> file_idx = index.Rtree('rtree')
   >>> file_idx.insert(1, (left, bottom, right, top))
   >>> file_idx.insert(2, (left - 1.0, bottom - 1.0, right + 1.0, top + 1.0))
@@ -191,7 +191,7 @@ stored on disk as the files ``3d_index.data`` and ``3d_index.index``::
   >>> p = index.Property()
   >>> p.dimension = 3
   >>> p.dat_extension = 'data'
-  >>> p.idx_extension = 'index'  
+  >>> p.idx_extension = 'index'
   >>> idx3d = index.Index('3d_index',properties=p)
   >>> idx3d.insert(1, (0, 60, 23.0, 0, 60, 42.0))
   >>> idx3d.intersection( (-1, 62, 22, -1, 62, 43))
@@ -200,9 +200,9 @@ stored on disk as the files ``3d_index.data`` and ``3d_index.index``::
 ZODB and Custom Storages
 ..............................................................................
 
-https://mail.zope.org/pipermail/zodb-dev/2010-June/013491.html contains a custom 
+https://mail.zope.org/pipermail/zodb-dev/2010-June/013491.html contains a custom
 storage backend for `ZODB`_
 
 .. _ZODB: http://www.zodb.org/
 
-.. _`libspatialindex`: https://libspatialindex.org/ 
+.. _`libspatialindex`: https://libspatialindex.org/