New Features and Bug Fixes since v0.2, preview 1 |
Fixes and Enhancements since Version 0.5 alpha 1 |
|
|
* Added a 'test' command to 'setup.py' that installs and then tests all of |
- Added 'binding.whenAssembled(...)' as syntax sugar for |
TransWarp. (It saves me time running the unit tests while I'm writing |
'binding.Once(...,activateUponAssembly=True)'. |
new code.) |
|
|
|
* Added warnings for detectable module-level modifications of mutables |
|
in modules which are used for inheritances or advice. Added an API |
|
function, 'configure(object, attr1=val, attr2=val,...)' to safely |
|
set attributes of mutables that might have been defined in a derived |
|
module. |
|
|
|
* Removed 'Meta.ClassInit' and '__class_init__' support. Use metaclass |
|
'__init__' methods instead; see 'TW.Database.DataModel.RecordTypeMC' |
|
for one example of the conversion. |
|
|
|
* Added 'SEF.bindToParent()', 'SEF.bindToNames()', and 'SEF.bindToSelf()' |
|
descriptors, to allow more flexible component parameter bindings. |
|
|
|
* Improved key integrity checks in DataModel: Record objects now disallow |
|
modification of key fields unless the old value is None, and cache |
|
collisions between records with supposedly unique keys will result in an |
|
AssertionError. |
|
|
|
* Added 'SET' method (ala WarpCORE's set_X procedures) to |
|
TW.Utils.MiniTable. |
|
|
|
* Added more docs to TW.Utils.Code, and removed 'iterFromEnd()' method |
|
from code objects. Added experimental 'nextSplit' index to codeIndex |
|
objects that does top-level block analysis to allow splitting a code |
|
object into smaller routines. |
|
|
|
* Fixed the "reference to rebound class within another class" problem |
|
with module inheritance, as reported by (who else?) Ulrich Eck. :) |
|
|
|
* Rewrote SEF "features" to use 'element.verbFeature()' style methods |
|
instead of 'element.feature.verb()' style. UML/XMI/Querying code |
|
still uses the old-style SEF framework, which is still available from |
|
'TW.SEF.FeatureObjects'. See the docs of 'TW.SEF.Basic.FeatureMC' |
|
and 'TW.API.Meta.MethodExporter' for details on how new-style methods |
|
work. |
|
|
|
* Fixed misc. bugs in 'DataModel', 'LDAPModel', 'Connections', and |
|
'TW.Caching' found by Ulrich Eck. Thanks Ulrich! Also, added a fix |
|
to ensure that non-existent records are invalidated by |
|
'RecordType.getItem()'. |
|
|
|
* Added basic Specialist implementation to 'TW.SEF.Basic', and reverted |
|
naming from 'TypeService' and 'ITypeService' to 'Specialist' and |
|
'ISpecialist'. Updated 'TW.SEF.Interfaces' to reflect "self"-less |
|
convention for documenting methods. |
|
|
|
* Dropped obsolete 'TW.Database.Records' module. |
|
|
|
* 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 |
- Removed 'LOG_XYZ' convenience functions from 'peak.api', and refactored |
the 'doc' directory to 'docs/html/reference'. |
'peak.running.logs' to use a PEP 282-like interface, 'running.ILogger'. |
|
Under the new scheme, messages must be sent to a specific entry point |
|
(e.g. 'self.logger.warning("foo")'). Components can bind an attribute |
|
directly to a logger object, or via configuration properties or utilities. |
|
PEAK components that do logging all define a 'logger' attribute, bound |
|
to a configuration property in the 'peak.logs' property namespace. By |
|
a default in 'peak.ini', 'peak.logs.*' is configured to output messages |
|
of 'WARNING' priority or higher to 'sys.stderr'. |
|
|
|
For compatibility with the PEP 282 logging package, a 'logging.logger:' |
|
URL scheme has been added; looking up the URL '"logging.logger:foo.bar"' |
|
is equivalent to 'logging.getLogger("foo.bar")', unless the 'logging' |
|
package is not available, in which case the configuration property |
|
'peak.logs.foo.bar' will be looked up in the target context of the |
|
lookup. Optionally, you can configure the 'logging.logger' URL scheme so |
|
that it only uses PEAK loggers, and never uses the PEP 282 loggers. |
|
|
|
- Added 'binding.metamethod()' wrapper for metaclass methods that might |
|
not be accessible from their instances if the instances (classes) also |
|
defined the method for *their* instances. You must now use this wrapper |
|
on any such metaclass-defined methods, as PEAK no longer works around |
|
this via the 'x.__class__.foo(x,...)' trick that was used previously. |
|
In particular, if you have metaclass definitions of 'getParentComponent', |
|
'_getConfigData', 'getComponentName', or 'notifyUponAssembly', you need |
|
to wrap them with 'binding.metamethod' now. |
|
|
|
- Fixed 'mof2py' generator script not working |
|
|
|
- Fixed model.Element not getting parent component set when passed as a |
|
constructor argument. |
|
|
|
- Fixed property/utility lookups not working correctly on model.* |
|
objects. |
|
|
|
- Fixed IndentedStream generating all-whitespace lines |
|
|
|
- Made 'NOT_GIVEN' and 'NOT_FOUND' recognizable by humans (they 'repr' |
|
and 'str' to their names) and by Python (they can be pickled, and |
|
when restored they come back as the same object). |
|
|
* Added 'CHANGES.txt' file. |
|