The peak.util.extremes module provides a production-quality
implementation of the Min and Max objects from PEP 326. While PEP
326 was rejected for inclusion in the language or standard library,
the objects described in it are useful in a variety of applications.
In PEAK, they have been used to implement generic functions (in
RuleDispatch and PEAK-Rules), as well as to handle scheduling and
time operations in the Trellis. Because this has led to each project
copying the same code, we've now split the module out so it can be
used independently.
input, ok fgs@
Installing SymbolType gives you access to the peak.util.symbols
module, previously available only by installing the full PEAK
toolkit. peak.util.symbols provides a Symbol type and two built-in
symbols that are used by PEAK: NOT_FOUND and NOT_GIVEN.
input, ok fgs@
peak.util.assembler is a simple bytecode assembler module that
handles most low-level bytecode generation details like jump offsets,
stack size tracking, line number table generation, constant and
variable name index tracking, etc. That way, you can focus your
attention on the desired semantics of your bytecode instead of on
these mechanical issues.
input, ok fgs@
Separating concerns into different objects makes it easier
to write reusable and separately-testable components. The AddOns
package (``peak.util.addons``) lets you manage concerns using
``AddOn`` classes.
input, ok fgs@
Split it into -main and -gnome, the latter providing gnome-specific
libsoup library. While here, prettify Makefile and set HOMEPAGE.
Tested in a bulk build by and ok jasper@
The aim of the decorator module it to simplify the usage of decorators
for the average programmer, and to popularize decorators by showing
various non-trivial examples
martynas@ ok.
