[Subversion] / PEAK / CHANGES.txt  

Diff of /PEAK/CHANGES.txt

Parent Directory | Revision Log

version 347, Sun Mar 17 22:01:20 2002 UTC version 1081, Mon May 5 19:08:05 2003 UTC
Line 1 
Line 1 
 New Features and Bug Fixes since v0.2, preview 1  Fixes and Enhancements since Version 0.5 alpha 1
   
  * Added basic Specialist implementation to 'TW.SEF.Basic', and reverted   - Added 'binding.whenAssembled(...)' as syntax sugar for
    naming from 'TypeService' and 'ITypeService' to 'Specialist' and     'binding.Once(...,activateUponAssembly=True)'.
    'ISpecialist'.  Updated 'TW.SEF.Interfaces' to reflect "self"-less  
    convention for documenting methods.  
   
  * Dropped obsolete 'TW.Database.Records' module.   - Removed 'LOG_XYZ' convenience functions from 'peak.api', and refactored
      '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 '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.  


Generate output suitable for use with a patch program
Legend:
Removed from v.347  
changed lines
  Added in v.1081

cvs-admin@eby-sarna.com

Powered by ViewCVS 1.0-dev

ViewCVS and CVS Help