Mercurial > piecrust2
view docs/api/00__index.md @ 666:81d9c3a3a0b5
internal: Get rid of the whole "sub cache" business.
* Compute cache keys up front, so the cache directory is only chosen once.
* Buffer up config variants to apply before loading the config. Makes it
possible to cache variant-resulting configs, too.
* Make a factory class to reuse the logic that creates the `PieCrust` object
correctly for multi-process workers and such.
* Add a test.
| author | Ludovic Chabant <ludovic@chabant.com> |
|---|---|
| date | Thu, 03 Mar 2016 08:22:41 -0800 |
| parents | 61d53d2163d6 |
| children | 94d7d5e38571 |
line wrap: on
line source
--- title: Code --- PieCrust can be extended with plugins in order to support additional features such as new [formatters][1], [processors][2], or [template engines][3] (among other things). [Creating a plugin][4] is very easy in itself, but requires making a `setuptools` package in order to be easily shared with other people. [1]: {{docurl('content/formatters')}} [2]: {{docurl('asset-pipeline')}} [3]: {{docurl('content/templating')}} [4]: {{apiurl('plugins')}}