Code quality varies between modules, from "beta" to "experimental |
Code quality varies between modules, from "beta" to "experimental |
pre-alpha". :) |
pre-alpha". :) |
|
|
|
|
Package Description |
Package Description |
|
|
PEAK is the "Python Enterprise Application Kit". If you develop |
PEAK is the "Python Enterprise Application Kit". If you develop |
on building your application. |
on building your application. |
|
|
PEAK tools can be used with other "Python Enterprise" frameworks such as |
PEAK tools can be used with other "Python Enterprise" frameworks such as |
Zope and the Python DBAPI to construct web-based, GUI, or command-line |
Zope, Twisted, and the Python DBAPI to construct web-based, GUI, or |
applications, interacting with any kind of storage, or with no storage |
command-line applications, interacting with any kind of storage, or with |
at all. Whatever the application type, PEAK can help you put it together. |
no storage at all. Whatever the application type, PEAK can help you put |
|
it together. |
|
|
Package Features |
Package Features |
|
|
components and thus more easily combine and "wire" them together. |
components and thus more easily combine and "wire" them together. |
|
|
* A comprehensive configuration framework that allows accessing |
* A comprehensive configuration framework that allows accessing |
"utilities" and "configuration properties" in-context. Properties |
"utilities" and "configuration properties" in context. Properties |
and utilities can be loaded or computed on demand, supplied by rules, |
and utilities can be loaded or computed on demand, supplied by rules, |
defined in configuration files or code, in a supplied or custom |
defined in configuration files or code, in a supplied or custom |
format. Properties and utilities are contextual and can be safely |
format. Properties and utilities are contextual and can be safely |
acquired from parent/context components automatically. System-wide |
acquired from parent/context components automatically. |
(per Python interpreter), application-wide (per running application |
|
within an interpreter) and per-component configuration settings |
|
are available. |
|
|
|
* Naming system/framework that's midway between J2EE's JNDI and CORBA's |
* Naming system/framework that's midway between J2EE's JNDI and CORBA's |
cosNaming in features, but much easier to use and extend than either |
cosNaming in features, but much easier to use and extend than either |
a given object type and storage approach, you can create your own |
a given object type and storage approach, you can create your own |
"DM" components. You can think of a DM as an advanced form of |
"DM" components. You can think of a DM as an advanced form of |
Python "shelve", that supports references to other objects, |
Python "shelve", that supports references to other objects, |
transactions, arbitrary back-end storages, and |
transactions, arbitrary back-end storages, and caching. |
|
|
- "Stackable" data managers: one DM might serialize a set of objects |
- "Stackable" data managers: one DM might serialize a set of objects |
to XML, which could then be stored in a database record by another |
to XML, which could then be stored in a database record by another |
that writes to disk files! Each DM only needs to know how to |
that writes to disk files! Each DM only needs to know how to |
manipulate objects offered by the next-level DM, not the details |
manipulate objects offered by the next-level DM, not the details |
of the next DM's implementation, so all the DM's are potentially |
of the next DM's implementation, so all the DM's are potentially |
replacable with alternate storage mechanisms. |
replaceable with alternate storage mechanisms. |
|
|
- RDBMS and LDAP connection framework based on the Python DBAPI, |
- RDBMS and LDAP connection framework based on the Python DBAPI, |
that handles data type conversions (via the configuration |
that handles data type conversions (via the configuration |
by name or URL, and bound as default collaborators or utilities |
by name or URL, and bound as default collaborators or utilities |
for access by other application components. |
for access by other application components. |
|
|
* CASE/modelling tools: PEAK includes APIs to read and write object |
* CASE/modelling tools: PEAK includes APIs to read object |
models created in the XML-based XMI format. Many open-source and |
models created in the XML-based XMI format. Many open-source and |
commercial modelling tools support XMI, inlcuding Argo/Poseidon and |
commercial modelling tools support XMI, inlcuding Argo/Poseidon and |
MagicDraw UML. PEAK includes pre-built support for UML versions 1.3 |
MagicDraw UML. PEAK includes pre-built support for UML version 1.3 |
and 1.4, CWM 1.1, and MOF 1.3.1, using XMI versions 1.0 through 1.2. |
and MOF 1.3.1, using XMI versions 1.0 and 1.1. (UML 1.4, UML 1.5, |
Also included, a MOF->Python code generator, which was used to generate |
CWM 1.0, CWM 1.1, and XMI 1.2 are anticipated for 0.5a2, and possibly |
the UML and CWM support, and which you can use to generate support for |
XMI 2.0 by 0.5 final.) Also included is a MOF->Python code generator, |
other modelling languages based on the MOF. |
which was used to generate the UML and CWM support, and which you can |
|
use to generate support for other modelling languages based on the MOF. |
|
|
For the specifications of XMI, MOF, CWM, and UML, visit: |
For the specifications of XMI, MOF, CWM, and UML, visit: |
http://www.omg.org/technology/documents/modeling_spec_catalog.htm |
http://www.omg.org/technology/documents/modeling_spec_catalog.htm |
from PEAK models (and vice versa) is possible (although |
from PEAK models (and vice versa) is possible (although |
not yet implemented for anything but MOF->PEAK). |
not yet implemented for anything but MOF->PEAK). |
|
|
|
* Application Runtime tools, including: |
|
|
|
- a "command objects" framework for creating command-line applications |
|
|
|
- a "periodic tasks" framework for executing tasks that perform "as |
|
needed", scheduling themselves in response to their available workloads |
|
|
|
- a CGI/FastCGI publishing framework that uses 'zope.publisher' to |
|
publish a PEAK component tree and its associated transaction service |
|
|
|
- an event-driven "reactor" framework that can be used with Twisted, |
|
or in place of it for many simpler "mostly scheduling" applications. |
|
|
* AOP and SOP: PEAK allows you to separate concerns as modules, then |
* AOP and SOP: PEAK allows you to separate concerns as modules, then |
combine the modules via a "module inheritance" technique. This |
combine the modules via a "module inheritance" technique. This |
lets you define a generated business object model as a |
lets you define a generated business object model as a |
in areas not covered by the test suites. Also, many system interfaces |
in areas not covered by the test suites. Also, many system interfaces |
are still subject to change. |
are still subject to change. |
|
|
PEAK includes early copies of Zope 3's 'Interface' and 'Persistence' |
PEAK includes early copies of Zope X3's 'zope.interface' and 'persistence' |
packages, which have since changed names in their official releases, |
packages, which have had - and will continue to have - significant |
and have had - and will continue to have - significant implementation |
implementation changes. We will be tracking Zope X3 periodically, but |
changes. Complete interoperability with Zope 3 is therefore currently |
can't guarantee compatibility with arbitrary (e.g. CVS) versions of |
at risk. We are waiting until the pending refactoring of Zope 3's |
Zope X3. |
interface package is complete before upgrading from 'Interface' to |
|
'zope.interface'. Also, the ZODB persistence package is undergoing |
|
some changes that may make it less useful for PEAK, and we may be |
|
forced to "fork" and/or create our own C-level persistence support. |
|
This may be clearer once ZODB4 and/or Zope 3 reach their next release. |
|
|
|
Documentation at present is limited, and scattered. The principal |
Documentation at present is limited, and scattered. The principal |
documentation is an API reference generated from the code's lengthy |
documentation is an API reference generated from the code's lengthy |
please see the 'src/kjbuckets/COPYRIGHT.txt' file for details of its |
please see the 'src/kjbuckets/COPYRIGHT.txt' file for details of its |
license. |
license. |
|
|
The 'Interface' and 'Persistence' packages are Copyright Zope Corporation |
The 'zope.interface', 'persistence', and 'ZConfig' packages are |
and contributors; please see the 'LICENSE.txt' files for details of their |
Copyright Zope Corporation and contributors; please see the 'LICENSE.txt' |
licenses. |
files in their directories for details of their licenses. |
|
|
|
|
Installation Instructions |
Installation Instructions |