of the way so that valuable screen real estate can be used for much more
important stuff. It has sane defaults and does not require one to learn a
language to do any configuration. It was written by hackers for hackers and it
strives to be small, compact and fast.
It was largely inspired by xmonad and dwm. Both are fine products but suffer
from things like: crazy-unportable-language-syndrome, silly defaults,
asymmetrical window layout, "how hard can it be?" and good old NIH.
Nevertheless dwm was a phenomenal resource and many good ideas and code was
borrowed from it. On the other hand xmonad has great defaults, key bindings
and xinerama support but is crippled by not being written in C.
WWW: http://www.peereboom.us/scrotwm/html/scrotwm.html
PR: ports/136214
Submitted by: Aragon Gouveia <aragon@phat.za.net>
dumpfiles as generated by tcpdump(1) or via live capture from an
interface using pcap(3) into bidirectional flows, then exports those
flows to IPFIX Collecting Processes or in an IPFIX-based file format.
YAF's output can be used with the SiLK flow analysis tools and any
other IPFIX compliant toolchain.
WWW: http://tools.netsa.cert.org/yaf/index.html
PR: ports/136118
Submitted by: Dikshie <dikshie at sfc.wide.ad.jp>
methods in order to to avoid AmbiguousMethods situations.This module
provides four decorators:
prioritized_when
prioritized_around
prioritized_before
prioritized_after
These behave like their peak.rules counterparts except that they accept
an optional prio argument which can be used to provide a comparable
object (usually an integer) that will be used to disambiguate situations
in which more than rule applies to the given arguments and no rule is
more specific than another. That is, situations in which an
peak.rules.AmbiguousMethods would have been raised.
This is useful for libraries which want to be extensible via generic
functions but want their users to easily override a method without
figuring out how to write a more specific rule or when it is not
feasible.
WWW: http://pypi.python.org/pypi/prioritized_methods/
PR: ports/136094
Submitted by: Wen Heping <wenheping at gmail.com>
is a beta release. All functions have now been implemented and most
have test suites; the exceptions include the modules involved in
export of MAGE-TAB documents, which are still a little experimental in
nature. The API is mostly finalised (and fully documented), but some
details may yet change where necessary to improve usability.
WWW: http://search.cpan.org/dist/Bio-MAGETAB/
PR: ports/136021
Submitted by: Wen Heping <wenheping at gmail.com>
and method namespaces. A concern implemented using add-ons can be added at
runtime to any object that either has a writable __dict__ attribute, or is
weak-referenceable.
AddOn classes are also like adapters, but rather than creating a new instance
each time you ask for one, an existing instance is returned if possible. In
this way, add-ons can keep track of ongoing state. For example, a Persistence
add-on might keep track of whether its subject has been saved to disk.
WWW: http://www.python.org/pypi/AddOns
PR: ports/135947
Submitted by: Wen Heping <wenheping at gmail.com>
generic functions, from the very simple to the very complex. Out of
the box, it supports multiple-dispatch on positional arguments using
tuples of types, full predicate dispatch using strings containing
Python expressions, and CLOS-like method combining. (But the framework
allows you to mix and match dispatch engines and custom method
combinations, if you need or want to.)
WWW: http://pypi.python.org/pypi/PEAK-Rules
PR: ports/135965
Submitted by: Wen Heping <wenheping at gmail.com>
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.
WWW: http://pypi.python.org/pypi/BytecodeAssembler
PR: ports/135945
Submitted by: Wen Heping <wenheping at gmail.com>
