No default branch
Bookmark a link to HEAD: (view) (download) (as text)
Added 'kjbuckets' extension to setup.py; updated installation doc and copyright notices accordingly.
Moved module inheritance/advice tests to peak.config.tests.
Changing docs from TransWarp->PEAK, referenced new site at http://www.telecommunity.com/PEAK/, prepping docs for 0.5a1 release.
Changed to not generate docs for Zope Interface package.
Made peak.storage a proper package and added it to setup.py. Added a 'finishTransaction()' message to the participant API, so that objects can be sure a transaction is really, and completely, over. Made the abstract TransactionService concrete by finishing out a few more methods and making it a binding.AutoCreated component. Now adding a transaction service to an application is as easy as 'myTxnAttribute = storage.TransactionService' in a high-level component. Also added a 'TransactionComponent' base class for things like managed connection objects and Racks. Instances automatically register with their nearest transaction service as soon as they're added to a component hierarchy. Last, but not least, I fleshed out the transaction metadata implementations for both the basic transaction service and the ZODB-compatible one. The ZODBTransactionService will interpret the names 'note', 'user_name' and 'user_path' as special, and call the note() and setUser() methods of the underlying ZODB transaction, accordingly. All other info items will be set via setExtendedInfo() on the underlying ZODB transaction.
Moved config to its own top-level subpackage, peak.config, since it doesn't really fit well with the rest of 'running' as it's shaping up. Also, removed lockfiles and dameons from the running.api, as they aren't really part of the API. Lockfiles will normally be instantiated via a URL reference, as will most Daemon providers. To create daemons, the preferred method will be: from peak.running import daemons class MyDaemon(daemons.AbstractDaemon): .... Similarly, when we have logging base classes, 'from peak.running import logs' and 'aLog = logs.SomeLogger()' will be reasonable usage as well, since logs will also normally be instantiated via URL references.
Added config package, and integrated it into binding.Component's acquireUtility() method. Note that the config API signatures ended up slightly different than in the implementation plan posted to the mailing list; notably, it didn't make sense to have 'forRoot' as an optional parameter, since *every* root needs its own local configuration, unless you manually set the same one for a bunch of them.
Added Interface package to setup. (If you're tracking CVS, be sure to "cvs update -dPA" to get the Interface directory to show up.)
Moved module inheritance from 'peak.api' to 'peak.binding', and reformatted peak.api package accordingly. Applied the following name changes:: .getSEFparent() -> .getParentComponent() ._setSEFparent() -> .setParentComponent() .getService() -> .lookupComponent() setupModule() -> binding.setupModule() adviseModule() -> binding.patchModule() configure() -> binding.configure() Also made the default '__proceed__' value a built-in, so that it's not necessary to import it. This concludes the essential code-level transformations from TransWarp to PEAK. Almost everything should be in its long-term home now, with its long-term name, although the 'model' package may receive some adjustments by the time a tutorial is written for it. Following this check-in, the repository will be considered stable, and CVS checkouts of PEAK will be possible.
Added naming package to setup, fixed a syntax error.
Hacked on it until all tests pass... But still a lot of re-name, re-doc, re-org to go. Still need to move Caching over, and there are some test package splits that need to be done (metamodels->model). Need to make the Once and other peak.binding package import idioms consistent, too. But at least the tests run. The repository is not yet stable, however.
First pass of random conversions from TW -> peak
Added 'TWX' package for extensions; added 'TWX.Diagrams.GraphViz' diagramming utility module. Very hacky and first-draft, with no unit tests, but I've manually verified most of the functionality so far.
Documented setup.py 'test' command, and added an option to specify which test module should be run.
Added a 'test' command to 'setup.py' that installs and then tests all of TransWarp. (It saves me time running the unit tests while I'm writing new code.)
Fixed 'happy' command not to build docs for 'tests' packages.
Many changes in preparation for 0.2 final, including: * Added 'SEF.bindToParent()' and 'SEF.bindToNames()' specifiers to allow more flexible component parameter bindings. * Fixed the base class "rebind by name" bugs in module inheritance, and updated the documentation to more clearly reflect what it is that metaclass generation and module inheritance does and does not do. Added test cases to prevent regression of the rebind-by-name problem. * The 'setup.py' script features a new command, 'happy', which can be used to generate the API reference docs, and this command runs as part of the 'sdist' command to build source distributions. * The API reference docs in the source distribution has been moved from the 'doc' directory to 'docs/html/reference'. * Added 'CHANGES.txt' file.
Updated website URL, and fixed MANIFEST.in to avoid including the (currently out-of-date) examples directory.
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...
Pre-release documentation and cleanup sweep, part 2. Cleaned up the rest of the 3-letter packages (SEF, MOF, and API), replacing StructuralModel with SEF along the way. Also moved some of the key metaclasses into their own module, TW.API.Meta.
Fixed the %&$#(@%& distutils data file path problem, after much Googling and Use of The Source.
Fixed bad data file path
Initial (untested) setup.py
Powered by ViewCVS 1.0-dev