Skip to main content

Grok-like configuration for catalog and indexes

Project description

Grok

What is grok?

Grok is a smashing web framework based on Zope Toolkit technology.

Grok uses the Component Architecture and builds on Zope concepts like content objects (models), views, and adapters. Its simplicity lies in using convention over configuration and sensible defaults when wiring components together. That means neither a configuration language like ZCML nor a lot of repetition are needed to create a web application with grok.

You can find out much more about Grok at our http://grok.zope.org website.

Who is grok?

Grok is a friendly caveman from the Stone Age. He has a big club that he hunts mammoths with. He will also use this club to smash anything he doesn’t like.

“ME GROK SMASH ZCML!”

Getting grok

The easiest way to get started with grok is to install the grokproject package (e.g. via easy_install grokproject) and then create a new project area by calling the grokproject script like so:

$ grokproject MyProject
... many lines of output here

This will create a project area in MyProject as well as download and install grok.

You can also get grok from the subversion repository:

svn co svn://svn.zope.org/repos/main/grok/trunk grok

Then follow the instructions of INSTALL.txt.

CHANGES

3.0.1 (2018-01-12)

  • Rearrange tests such that Travis CI can pick up all functional tests too.

3.0.0 (2018-01-05)

  • Python 3 compatibility.

2.3 (2017-08-11)

  • Introduce IntId index that is more optimized to index values by their int ids.

2.2.1 (2016-01-29)

  • Update tests.

2.2 (2015-11-20)

  • Introduce Datetime index that’s more optimized for index datetime objects. Please note the index uses seconds-resolution (the integer timestamp representing the datetime’s value).

2.1 (2015-06-11)

  • Make possible to install a catalog in a site on a different event than IObjectAddedEvent using the grokcore.site.install_on directive.

2.0 (2013-05-07)

  • Rename IIndexDefinition and IndexDefinition into IAttributeIndexDefinition and AtributeIndexDefinition respectively. This is used for the current index “classes” and allow for setup() magic for attribute indexes when creating new catalogs.

    This allows for IIndexDefinition and IndexDefinition to be used for simpler catalog index definitions where no Grok magic is applied when creating catalogs.

1.0 (2012-05-01)

  • Initial fork from Grok.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

grokcore.catalog-3.0.1.tar.gz (20.6 kB view details)

Uploaded Source

File details

Details for the file grokcore.catalog-3.0.1.tar.gz.

File metadata

File hashes

Hashes for grokcore.catalog-3.0.1.tar.gz
Algorithm Hash digest
SHA256 f2aa5029da0a26733708ff05a2b91f669b1255d5049edf90e64c7d7c02b877ee
MD5 4c5065c8e6cca09440b214dc8b4a0665
BLAKE2b-256 3b292f760c2fd95d94fce4c4dfd7e20cfcaaa8a2994e698c62bf5e082240bad4

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page