/usr/share/pyshared/zope.index-3.6.4.egg-info/PKG-INFO is in python-zope.index 3.6.4-0ubuntu1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 | Metadata-Version: 1.0
Name: zope.index
Version: 3.6.4
Summary: Indices for using with catalog like text, field, etc.
Home-page: http://pypi.python.org/pypi/zope.index
Author: Zope Foundation and Contributors
Author-email: zope-dev@zope.org
License: ZPL 2.1
Description: Overview
--------
The ``zope.index`` package provides several indices for the Zope
catalog. These include:
* a field index (for indexing orderable values),
* a keyword index,
* a topic index,
* a text index (with support for lexicon, splitter, normalizer, etc.)
Changes
=======
3.6.4 (2012-03-12)
------------------
- Insure proper unindex behavior if index_doc is called with a empty sequence.
- Use the standard Python doctest module instead of zope.testing.doctest
3.6.3 (2011-12-03)
------------------
- KeywordIndex: Minor optimization; use __nonzero__ instead of __len__
to avoid loading the full TreeSet.
3.6.2 (2011-12-03)
------------------
- KeywordIndex: Store docids in TreeSet rather than a Set when the
number of documents matching a word reaches a configurable
threshold (default 64). The rule is applied to individual words at
indexing time, but you can call the new optimize method to optimize
all the words in an index at once. Designed to fix LP #881950.
3.6.1 (2010-07-08)
------------------
- TextIndex: reuse the lexicon from the underlying Okapi / Cosine
index, if passed. (LP #232516)
- Lexicon: avoid raising an exception when indexing None. (LP #598776)
3.6.0 (2009-08-03)
------------------
- Improved test readability and reached 100% test coverage.
- Fixed a broken optimization in okascore.c: it was passing a Python
float to the PyInt_AS_LONG() macro. This resulted in wrong scores,
especially on 64 bit platforms, where all scores typically ended up
being zero.
- Changed okascore.c to produce the same results as its Python
equivalent, reducing the brittleness of the text index tests.
3.5.2 (2009-06-09)
------------------
- Port okascore.c optimization used in okapiiindex from Zope2 catalog
implementation. This module is compiled conditionally, based on
whether your environment has a working C compiler.
- Don't use ``len(self._docweight)`` in okapiindex _search_wids method
(obtaining the length of a BTree is very expensive at scale).
Instead use self.documentCount(). Also a Zope2 port.
3.5.1 (2009-02-27)
------------------
- The baseindex, okapiindex, and lexicon used plain counters for various
lengths, which is unsuitable for production applications.
Backport code from Zope2 indexes which opportunistically replaces the
counters with BTree.Length objects.
- Backport non-insane version of baseindex._del_wordinfo from
Zope2 text index. This improves deletion performance by
several orders of magnitude.
- Don't modify given query dictionary in the KeywordIndex.apply method.
- Move FieldIndex's sorting functionality to a mixin class so it can
be reused by zc.catalog's ValueIndex.
3.5.0 (2008-12-30)
------------------
- Remove zope.testing from dependencies, as it's not really needed.
- Define IIndexSort interface for indexes that support sorting.
- Implement sorting for FieldIndex (adapted from repoze.catalog/ZCatalog).
- Add an ``apply`` method for KeywordIndex/TopicIndex, making them
implement IIndexSearch that can be useful in catalog.
- Optimize the ``search`` method of KeywordIndex/TopicIndex by using
multiunion for the ``or`` operator and sorting before intersection for ``and``.
- IMPORTANT: KeywordIndex/TopicIndex now use IFSets instead of IISets.
This makes it more compatible with other indexes (for example, when
using in catalog). This change can lead to problems, if your code somehow
depends on the II nature of sets, as it was before.
Also, FilteredSets used to use IFSets as well, if you have any
FilteredSets pickled in the database, you need to migrate them to
IFSets yourself. You can do it like that:
filter._ids = filter.family.IF.Set(filter._ids)
Where ``filter`` is an instance of FilteredSet.
- IMPORTANT: KeywordIndex are now non-normalizing. Because
it can be useful for non-string keywords, where case-normalizing
doesn't make any sense. Instead, it provides the ``normalize``
method that can be overriden by subclasses to provide some
normalization.
The CaseInsensitiveKeywordIndex class is now provided that
do case-normalization for string-based keywords. The old
CaseSensitiveKeywordIndex is gone, applications should use
KeywordIndex for that.
Looks like the KeywordIndex/TopicIndex was sort of abadonware
and wasn't used by application developers, so after some
discussion we decided to refactor them to make them more
usable, optimal and compatible with other indexes and catalog.
Porting application from old KeywordIndex/TopicIndex to new
ones are rather easy and explained above, so we believe that
it isn't a problem. Please, use zope3-users@zope.org or
zope-dev@zope.org mailing lists, if you have any problems
with migration.
Thanks Chris McDonough of repoze for supporting and useful code.
3.4.1 (2007-09-28)
------------------
- Fixed bug in package metadata (wrong homepage URL).
3.4.0 (2007-09-28)
------------------
No further changes since 3.4.0a1.
3.4.0a1 (2007-04-22)
--------------------
Initial release as a separate project, corresponds to zope.index from
Zope 3.4.0a1
Platform: UNKNOWN
|