> Catalog doesn't take the Vocabulary object itself as an argument. It
> takes the (string) id of an acquirable Vocabulary. If you don't specify
> a string, it creates a standard non-globbing lexicon (Although a
> ZCatalog creates a globbing lexicon, go figure). Something like this
> should work (
Casey Duncan wrote:
> [EMAIL PROTECTED] wrote:
> >
> > I tried both
> >
> >my_catalog = Catalog(GlobbingLexicon())
> >
> > and
> >
> >my_catalog = Catalog(Vocabulary(globbing=1))
> >
> > and neither resulted in any calls to any GlobbingLexicon methods!
> >
> > Richard
> >
>
> Catalog
[EMAIL PROTECTED] wrote:
>
> I tried both
>
>my_catalog = Catalog(GlobbingLexicon())
>
> and
>
>my_catalog = Catalog(Vocabulary(globbing=1))
>
> and neither resulted in any calls to any GlobbingLexicon methods!
>
> Richard
>
Catalog doesn't take the Vocabulary object itself as
Casey Duncan wrote:
>
> [EMAIL PROTECTED] wrote:
> >
> > We're using the internals of ZCatalog to do searching stuff in our Python
> > Product. I've managed to get it working at a basic level by constructing a
> > Catalog instance and adding indexes and calling searchResults(). Only now I
> > nee
[EMAIL PROTECTED] wrote:
>
> We're using the internals of ZCatalog to do searching stuff in our Python
> Product. I've managed to get it working at a basic level by constructing a
> Catalog instance and adding indexes and calling searchResults(). Only now I
> need to get into more advanced featur
We're using the internals of ZCatalog to do searching stuff in our Python
Product. I've managed to get it working at a basic level by constructing a
Catalog instance and adding indexes and calling searchResults(). Only now I
need to get into more advanced features, like partial word matches and
mu
