[Checkins] SVN: zc.catalog/trunk/src/zc/catalog/ whitespace fixes

Benji York benji at zope.com
Thu Sep 14 11:35:26 EDT 2006


Log message for revision 70175:
  whitespace fixes
  

Changed:
  U   zc.catalog/trunk/src/zc/catalog/extentcatalog.txt
  U   zc.catalog/trunk/src/zc/catalog/normalizedindex.txt
  U   zc.catalog/trunk/src/zc/catalog/setindex.txt
  U   zc.catalog/trunk/src/zc/catalog/valueindex.txt

-=-
Modified: zc.catalog/trunk/src/zc/catalog/extentcatalog.txt
===================================================================
--- zc.catalog/trunk/src/zc/catalog/extentcatalog.txt	2006-09-14 15:00:05 UTC (rev 70174)
+++ zc.catalog/trunk/src/zc/catalog/extentcatalog.txt	2006-09-14 15:35:25 UTC (rev 70175)
@@ -2,7 +2,7 @@
 indexes items addable to its extent.  The extent is both a filter and a
 set that may be merged with other result sets.
 
-To show the extent catalog at work, we need an intid utility, an index, 
+To show the extent catalog at work, we need an intid utility, an index,
 some items to index, and a filter that determines what the extent accepts.
 
     >>> from zc.catalog import interfaces, extentcatalog
@@ -68,7 +68,7 @@
     >>> index = DummyIndex()
     >>> catalog['index'] = index
 
-Now we have a catalog set up with an index and an extent, and some content to 
+Now we have a catalog set up with an index and an extent, and some content to
 index.  If we ask the catalog to index all of the content, only the ones that
 match the filter will be in the extent and in the index.
 
@@ -80,7 +80,7 @@
     >>> list(sorted(extent)) == list(sorted(index.uids)) == matches
     True
 
-If a content object is indexed that used to match the filter but no longer 
+If a content object is indexed that used to match the filter but no longer
 does, it should be removed from the extent and indexes.
 
     >>> 5 in catalog.extent
@@ -109,7 +109,7 @@
     >>> list(sorted(extent)) == list(sorted(index.uids)) == matches
     True
 
-And similarly, unindexing an object that is not in the catalog should be a 
+And similarly, unindexing an object that is not in the catalog should be a
 no-op.
 
     >>> 0 in catalog.extent
@@ -166,12 +166,12 @@
     True
 
 The extent itself provides a number of merging features to allow its values to
-be merged with other BTrees.IFBTree data structures.  These include 
-intersection, union, difference, and reverse difference.  Given an extent 
+be merged with other BTrees.IFBTree data structures.  These include
+intersection, union, difference, and reverse difference.  Given an extent
 named 'extent' and another IFBTree data structure named 'data', intersections
-can be spelled "extent & data" or "data & extent"; unions can be spelled 
+can be spelled "extent & data" or "data & extent"; unions can be spelled
 "extent | data" or "data | extent"; differences can be spelled "extent - data";
-and reverse differences can be spelled "data - extent".  Unions and 
+and reverse differences can be spelled "data - extent".  Unions and
 intersections are weighted.
 
     >>> from BTrees import IFBTree

Modified: zc.catalog/trunk/src/zc/catalog/normalizedindex.txt
===================================================================
--- zc.catalog/trunk/src/zc/catalog/normalizedindex.txt	2006-09-14 15:00:05 UTC (rev 70174)
+++ zc.catalog/trunk/src/zc/catalog/normalizedindex.txt	2006-09-14 15:35:25 UTC (rev 70175)
@@ -7,7 +7,7 @@
 and delegates all of the behavior to the wrapped index, normalizing values
 using the normalizer before the index sees them.
 
-The normalizing wrapper currently only supports queries offered by 
+The normalizing wrapper currently only supports queries offered by
 zc.catalog.interfaces.ISetIndex and zc.catalog.interfaces.IValueIndex.
 
 The normalizer interface requires the following methods, as defined in the
@@ -39,7 +39,7 @@
 that (no request or no adapter) it uses the system local timezone.
 
 - input values must be datetimes with a timezone.  They are normalized to the
-  resolution specified when the normalizer is created: a resolution of 0 
+  resolution specified when the normalizer is created: a resolution of 0
   normalizes values to days; a resolution of 1 to hours; 2 to minutes; 3 to
   seconds; and 4 to microseconds.
 
@@ -48,7 +48,7 @@
   given date in the found timezone, as described above.  timezone-naive
   datetimes get the found timezone.
 
-- 'all' values may be timezone-aware datetimes or timezone-naive datetimes. 
+- 'all' values may be timezone-aware datetimes or timezone-naive datetimes.
   timezone-naive datetimes get the found timezone.
 
 - 'minimum' values may be timezone-aware datetimes, timezone-naive datetimes,
@@ -94,7 +94,7 @@
 Note that changing the resolution of an indexed value may create surprising
 results, because queries do not change their resolution.  Therefore, if you
 index something with a datetime with a finer resolution that the normalizer's,
-then searching for that datetime will not find the doc_id.  
+then searching for that datetime will not find the doc_id.
 
 Values in an 'any_of' query are parsed with 'any'.  'any' should return a
 sequence of values.  It requires an index, which we will mock up here.

Modified: zc.catalog/trunk/src/zc/catalog/setindex.txt
===================================================================
--- zc.catalog/trunk/src/zc/catalog/setindex.txt	2006-09-14 15:00:05 UTC (rev 70174)
+++ zc.catalog/trunk/src/zc/catalog/setindex.txt	2006-09-14 15:35:25 UTC (rev 70175)
@@ -49,7 +49,7 @@
     ...     index.index_doc(k, v)
     ...
 
-After indexing, the statistics and values match the newly entered content. 
+After indexing, the statistics and values match the newly entered content.
 
     >>> list(index.values())
     [1, 2, 3, 4, 5, 6, 7, 'a', 'b', 'c']
@@ -107,8 +107,8 @@
     >>> list(index.apply({'all_of': (3, 4)}))
     [2, 9]
 
-The 'between' argument takes from 1 to four values.  The first is the 
-minimum, and defaults to None, indicating no minimum; the second is the 
+The 'between' argument takes from 1 to four values.  The first is the
+minimum, and defaults to None, indicating no minimum; the second is the
 maximum, and defaults to None, indicating no maximum; the next is a boolean for
 whether the minimum value should be excluded, and defaults to False; and the
 last is a boolean for whether the maximum value should be excluded, and also
@@ -166,7 +166,7 @@
     >>> list(index.ids())
     [1, 2, 3, 4, 5, 7, 8, 9]
 
-Reindexing a document that has new additional values also is reflected in 
+Reindexing a document that has new additional values also is reflected in
 subsequent searches and statistic checks.
 
     >>> data[8].extend([5, 'c'])
@@ -215,7 +215,7 @@
     >>> list(index.apply({'none': extent}))
     [0, 2, 6, 10, 11, 12, 13, 14]
 
-The values method can be used to examine the indexed values for a given 
+The values method can be used to examine the indexed values for a given
 document id.
 
     >>> set(index.values(doc_id=8)) == set([1, 5, 6, 'c'])
@@ -228,4 +228,4 @@
     True
     >>> index.containsValue(20)
     False
-    
+

Modified: zc.catalog/trunk/src/zc/catalog/valueindex.txt
===================================================================
--- zc.catalog/trunk/src/zc/catalog/valueindex.txt	2006-09-14 15:00:05 UTC (rev 70174)
+++ zc.catalog/trunk/src/zc/catalog/valueindex.txt	2006-09-14 15:35:25 UTC (rev 70175)
@@ -48,7 +48,7 @@
     ...     index.index_doc(k, v)
     ...
 
-After indexing, the statistics and values match the newly entered content. 
+After indexing, the statistics and values match the newly entered content.
 
     >>> list(index.values())
     ['a', 'b', 'c', 'd']
@@ -97,8 +97,8 @@
     >>> list(index.apply({'any': limited_extent}))
     [1, 2, 3, 4]
 
-The 'between' argument takes from 1 to four values.  The first is the 
-minimum, and defaults to None, indicating no minimum; the second is the 
+The 'between' argument takes from 1 to four values.  The first is the
+minimum, and defaults to None, indicating no minimum; the second is the
 maximum, and defaults to None, indicating no maximum; the next is a boolean for
 whether the minimum value should be excluded, and defaults to False; and the
 last is a boolean for whether the maximum value should be excluded, and also
@@ -154,7 +154,7 @@
     >>> list(index.ids())
     [1, 2, 3, 4, 6, 7, 8, 9]
 
-Reindexing a document that has a changed value also is reflected in 
+Reindexing a document that has a changed value also is reflected in
 subsequent searches and statistic checks.
 
     >>> list(index.apply({'any_of': ('b',)}))
@@ -202,7 +202,7 @@
     >>> list(index.apply({'none': extent}))
     [0, 3, 5, 10, 11, 12, 13, 14]
 
-The values method can be used to examine the indexed values for a given 
+The values method can be used to examine the indexed values for a given
 document id.  For a valueindex, the "values" for a given doc_id will always
 have a length of 0 or 1.
 
@@ -216,4 +216,4 @@
     True
     >>> index.containsValue('q')
     False
-    
+



More information about the Checkins mailing list