No default branch
Bookmark a link to HEAD: (view) (download)
PEAK no longer bundles any software that can be obtained automatically from PyPI. Running PEAK's setup script will attempt to download and install the needed packages. (Note that development snapshots of PEAK may require development snapshots of related packages.)
PEAK now requires Python 2.3.4 or better; dropped support for building 2.3 modules with 2.2. The kjbuckets extension module is no longer built and installed by default, either; you must explicitly enable it with a '--with-kjbuckets' flag passed to 'setup.py'. Please port your code as soon as practical, this option will go away soon.
Overhaul setup.py to simplify installation and maintenance. It's no longer necessary to manually add packages or files to setup.py. Optional features can now be controlled with '--with-X' and '--without-X' options. Bumped version number to 0.5a4. (XXX Need to update INSTALL.txt w/options info!)
Added "state of the PEAK union" doc (STATUS.txt). Moved old changes to HISTORY.txt. Updated copyright and package info. Moved ancient and improbable TODO's out to individual packages. Readjust a3 TODO targets so we can release it a lot sooner, preferably within 1-3 weeks.
The templates have landed! We can parse and render templates, and use them as web methods on locations. There's even a (yes, just one) unit test. Big TODO lists both in the package and its test suite, but at least it's working. Made minor adjustments to publishing algorithms so that locations know their parent locations, and methods know the location that they were found in. Bumped package version to 0.5a3, since we've been in the alpha 3 cycle for a while now.
Added more #! docs.
Added Python/Zope 'datetime' package.
Misc. doc cleanups/enhancements. Added info on 'invoke' command.
Updated installation instructions to note that Zope X3 must be up-to-date if you have it installed on your Python path.
Misc. edits preparing for 0.5a2
Added a 'peak.running.shortcuts' command to run the unit tests. Now I'm also testing the command subsystem every time I run the tests... :)
Began the move of 'peak.interface' to a separate 'protocols' package for ease of distribution independently of PEAK. Also, removed caching of success/failed adapter lookups, because there was no way for them to be cleared when declarations were made for base classes of a class whose lookup was cached. (To do caching, I'll have to add a separate cache.) In the next pass, I'll add the new declaration API that Ty and I designed, and then change PEAK to use it, factoring out the interim API, and changing the few remaining introspections in PEAK to work via adapation. Then, it's off to documentation, unit tests, and packaging for the 'protocols' package.
Farewell, 'zope.interface'. You served us well.
Added notes about C and Pyrex to installation instructions; misc. edits.
Fixed misidentification of Zope 3 packages.
Added 'fcgiapp' to distribution; this should be the final checkin for 0.5a1, barring any bug or doc fixes that come up while prepping the release.
Updating README/INSTALL/setup for 0.5a1. INSTALL was out of date on some matters; edited README for clarity in a couple of places.
Fixed certain setup.py operations failing if HappyDoc isn't installed; minor updates to copyright notices and installation instructions.
Re-org/refactoring of many items from the TODO list for 0.5, including: * moved peak.binding.imports -> peak.util.imports, added importSuite() * Decided not to do binding.Acquire, it should just be a documented idiom * Moved LDAP and lockfile URLs to peak.storage.LDAP and peak.running.lockfiles, respectively * Moved factories.getObjectInstance -> spi, updated peak.ini to load naming.spi as the provider. * Consolidated naming.references into naming.names * Made ParsedURLs compile their pattern strings, and automatically make their 'fromX()' methods classmethods (and the same is true for other 'struct' types. * Refactored cursors and connections out into distinct SQLCursor/LDAPCursor types, based on a common AbstractCursor. * Added TooManyResults/TooFewResults errors to peak.exceptions
Updated for inclusion of fixed Interface and the bundled Persistence package.
Added 'kjbuckets' extension to setup.py; updated installation doc and copyright notices accordingly.
Changing docs from TransWarp->PEAK, referenced new site at http://www.telecommunity.com/PEAK/, prepping docs for 0.5a1 release.
Documented setup.py 'test' command, and added an option to specify which test module should be run.
Misc. Documentation fixes, clarifications, and enhancements.
Pre-release documentation and cleanup sweep, part 3. Rearranged all the test stuff to meet Zope.org's test packaging conventions. Added module docstrings to the Database package, and shuffled a few things around there to break up the code better. Looks like the last package left for this treatment is Utils...
First-draft README and INSTALL for 0.2 preview release 1.
Powered by ViewCVS 1.0-dev