py-AddOn classes are like dynamic mixins, but with their own private attribute 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.
12 lines
494 B
Text
12 lines
494 B
Text
@comment $NetBSD: PLIST,v 1.1.1.1 2010/07/14 13:10:27 jihbed Exp $
|
|
${PYSITELIB}/${EGG_NAME}-nspkg.pth
|
|
${PYSITELIB}/${EGG_INFODIR}/PKG-INFO
|
|
${PYSITELIB}/${EGG_INFODIR}/SOURCES.txt
|
|
${PYSITELIB}/${EGG_INFODIR}/dependency_links.txt
|
|
${PYSITELIB}/${EGG_INFODIR}/namespace_packages.txt
|
|
${PYSITELIB}/${EGG_INFODIR}/requires.txt
|
|
${PYSITELIB}/${EGG_INFODIR}/top_level.txt
|
|
${PYSITELIB}/peak/util/addons.py
|
|
${PYSITELIB}/peak/util/addons.pyc
|
|
${PYSITELIB}/peak/util/addons.pyo
|
|
share/doc/py-addons/README.txt
|