Mercurial > piecrust2
view docs/pages/support.md @ 440:32c7c2d219d2
performance: Refactor how data is managed to reduce copying.
* Make use of `collections.abc.Mapping` to better identify things that are
supposed to look like dictionaries.
* Instead of handling "overlay" of data in a dict tree in each different data
object, make all objects `Mapping`s and handle merging at a higher level
with the new `MergedMapping` object.
* Since this new object is read-only, remove the need for deep-copying of
app and page configurations.
* Split data classes into separate modules.
author | Ludovic Chabant <ludovic@chabant.com> |
---|---|
date | Sun, 28 Jun 2015 08:22:39 -0700 |
parents | c750dc21d55d |
children | 0c3b811d2c26 |
line wrap: on
line source
--- title: Support header_class: support --- If you have a problem with PieCrust, there are a few ways to solve it: * Check the [documentation][doc] one more time! You never know, the solution may be in there. * Is the documentation wrong or missing something? If you know what must be fixed, you can get the source from [BitBucket][bbsrc] or [Github][ghsrc] and make a pull request. * If you're pretty sure you found a bug, please file a report on [BitBucket][bbbug] or [Github][ghbug]. If by chance you've already fixed it, even better! Make a pull request, you know the drill. * If you have questions, hit the [me][] on [Twitter][]. [doc]: {{docurl('')}} [bbsrc]: https://bitbucket.org/ludovicchabant/piecrust2 [bbbug]: https://bitbucket.org/ludovicchabant/piecrust2/issues?status=new&status=open [ghsrc]: https://github.com/ludovicchabant/PieCrust2 [ghbug]: https://github.com/ludovicchabant/PieCrust2/issues [me]: http://ludovic.chabant.com [twitter]: https://www.twitter.com/ludovicchabant