| |
|
| Targeted for 0.5 Alpha 2 |
Targeted for 0.5 Alpha 2 |
| |
|
| * Finish 'protocols' breakout and prepare for possible PEP |
* Finish 'protocols' breakout |
| |
|
| - Add reference docs |
- Finish reference docs |
| |
|
| - Create tutorial |
- Publish/link to the docs from PEAK tutorial and main website |
| |
|
| |
- Tests for 'Attribute' class |
| |
|
| * ZConfig Integration |
* ZConfig Integration |
| |
|
| |
|
| Targeted for 0.5 Beta 1 |
Targeted for 0.5 Beta 1 |
| |
|
| * Updated reference docstrings for 'peak.api', 'peak.binding', |
* Up-to-date reference docstrings for all packages |
| 'peak.config', 'peak.exceptions', and 'peak.naming'. |
|
| |
|
| * Finish tutorial chapter 2 (?) |
* Finish tutorial chapter 2 (?) |
| |
|
| |
|
| |
|
| |
|
| |
|
| Targeted for 0.5 Final Release (or sooner) |
Targeted for 0.5 Final Release (or sooner) |
| |
|
| General |
|
| |
|
| * Tutorial complete through chapter 4 |
|
| |
|
| peak.storage |
peak.storage |
| |
|
| - unit tests for more complex object scenarios: references, thunks..? |
- unit tests for more complex object scenarios: references, thunks..? |
| |
|
| - lock management interfaces/API |
|
| |
|
| - docstrings for reference |
|
| |
|
| peak.model |
|
| |
|
| - clean up TW docstrings & interfaces |
|
| |
|
| peak.naming |
peak.naming |
| |
|
| - useful example "flat" naming context (e.g. like AppUtils.URLkeys) |
- useful example "flat" naming context (e.g. like AppUtils.URLkeys) |
| |
|
| - useful example hierarchical naming context (e.g. like JNDI's LDAP |
- useful example hierarchical naming context (e.g. like JNDI's LDAP |
| context or filesystem context) |
context or a filesystem context) |
| |
|
| - rework smtp: to return a factory object that supports open(). |
- rework smtp: to return a factory object that supports open(). |
| Also think about whether smtp should move elsewhere. Maybe |
Also think about whether smtp should move elsewhere. Maybe |
| there should be peak.network or peak.internet for things like |
there should be peak.network or peak.internet for things like |
| smtp, ftp, etc contexts? |
smtp, ftp, etc contexts? |
| |
|
| peak.running |
- add in Ty's cool "n2" (Namespace Navigator) shell for working with |
| |
naming providers. |
| - make 'cluster' parser complain about things that would cause |
|
| the clusterit tools to choke or barf on the file, or which would |
|
| produce ambiguous or unintended results. |
|
| |
|
| - simple daemons comparable to those in MetaDaemon, unit tests |
|
| |
|
| - docstrings for reference |
|
| |
|
| |
|
| peak.config |
|
| |
|
| - "Rule"-oriented configuration files (section specifies component |
|
| rather than property name prefix), so that daemons and other simple |
|
| apps can be fully configured and run via a config file. |
|
| |
|
| peak.util |
|
| |
|
| - docstrings for reference |
|
| |
|
| - more unit tests? |
|
| |
|
| |
|
| Targeted for version 0.6 |
Targeted for version 0.6 |
| 'setup.py' package lists. |
'setup.py' package lists. |
| |
|
| * On-the-fly class combination (think "runtime module inheritance", |
* On-the-fly class combination (think "runtime module inheritance", |
| without the modules) for DMs. |
but possibly without the modules) for DMs. |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
* Lock management interfaces/API for peak.storage |
| |
|
| |
* Make 'cluster' parser complain about things that would cause |
| |
the clusterit tools to choke or barf on the file, or which would |
| |
produce ambiguous or unintended results. (Or replace with ZConfig |
| |
schema that can generate clusterit files. And/or replace clusterit |
| |
tools with PEAK ones.) |
| |
|
| |
|
| Future Releases |
Future Releases |
Diff of /PEAK/TODO.txt
Parent Directory
| 
Revision Log