[Subversion] / PEAK / CHANGES.txt  

Diff of /PEAK/CHANGES.txt

Parent Directory | Revision Log

version 1097, Fri May 9 18:31:42 2003 UTC version 1104, Sat May 10 18:23:04 2003 UTC
Line 2 
Line 2 
   
  Changed, Enhanced, or Newly Deprecated Features   Changed, Enhanced, or Newly Deprecated Features
   
    - DEPRECATED use of '__implements__' and '__class_implements__' to declare
      support for interfaces.  Use 'implements()', 'classProvides()',
      'directlyProvides()', 'moduleProvides()', etc. to do this now; they
      are now available automatically from 'peak.api'.
   
    - The signatures of the 'getObjectInstance()', 'getStateToBind()', and
      'getURLContext()' methods in the 'peak.naming' package have changed, to
      place the context or parent component as the first, non-optional argument.
      (If you don't know what these methods are for, you don't need to do anything
      about this, as they are part of the naming package's extensibility
      framework.)
   
    - 'EigenRegistry' and 'PropertyMap' no longer attempt to figure out whether
      implied (i.e. inherited) interfaces are more or less general with respect
      to a previous registration.  This was behavior that emulated Zope adapter
      registries, but what we really wanted was more akin to a Zope "type"
      registry.  The only parts of the test suite that used the old behavior
      were the tests specifically written to ensure that behavior!
   
    - 'binding.bindTo()' now accepts a 'default=' argument, whose value will be
      used in case of a 'NameNotFound' error.
   
  - DEPRECATED 'naming.ParsedURL'.  It will disappear in 0.5 alpha 3 or beta.   - DEPRECATED 'naming.ParsedURL'.  It will disappear in 0.5 alpha 3 or beta.
    It is replaced by the new 'naming.URL.Base'.  The 'naming.URL' package     It is replaced by the new 'naming.URL.Base'.  The 'naming.URL' package
    provides a new URL parsing framework based on 'peak.model'.  Upgrading from     provides a new URL parsing framework based on 'peak.model'.  Upgrading from
Line 57 
Line 79 
   
  Corrected Problems   Corrected Problems
   
    - Fixed 'naming.lookup()' and related APIs not setting the parent component
      of created objects without an explicitly supplied 'creationParent' keyword
      argument.  This used to "sort of work" when we had implicit configuration
      parents, but was broken when we went "all explicit" for 0.5 alpha 1.
   
  - Fixed a problem where initializing single-valued immutable fields of   - Fixed a problem where initializing single-valued immutable fields of
   'peak.model' types did not perform type/value normalization.    'peak.model' types did not perform type/value normalization.
   

Generate output suitable for use with a patch program
Legend:
Removed from v.1097  
changed lines
  Added in v.1104
cvs-admin@eby-sarna.com

Powered by ViewCVS 1.0-dev

ViewCVS and CVS Help