PSARC,

I am sponsoring this case for Ghee Teo of the JDS - Gnome 
group in Dublin, Ireland.  The case directory contains this
proposal.  I have set the timeout for Tuesday, February 26th,
2008.


The project proposes to integrate the Python zope interfaces
into a minor release of Solaris.  The Zope component architecture 
is about how to create reusable components, but not the reusable
components itself.  Other Python modules will depend upon the
Zope interface architecture.

Thanks,

John
-------------- next part --------------
1. Introduction
   1.1. Project/Component Working Name:

        Python zope-interfaces

   1.2. Name of Document Author/Supplier:

        Ghee Teo

   1.3. Date of This Document:

        02/18/2008
        
   1.3.1. Date this project was conceived:

        November, 1998

   1.4. Name of Major Document Customer(s)/Consumer(s):

        1.4.1. The PAC or CPT you expect to review your project:

                Solaris PAC

        1.4.2. The ARC(s) you expect to review your project:

                PSARC

        1.4.3. The Director/VP who is "Sponsoring" this project:

                robert.odea at sun.com

        1.4.4. The name of your business unit:

                New Solaris / OpenSource.

   1.5. Email Aliases:
        1.5.1. Responsible Manager:

                leo.binchy at sun.com

        1.5.2. Responsible Engineer:

                Ghee.Teo at sun.com

        1.5.3. Marketing Manager:

                dan.roberts at sun.com

        1.5.4. Interest List:

                desktop-discuss at opensolaris.org

4. Technical Description:
    4.1. Details:

        This package provides the python zope Interface module. This module is 
    part of the Zope 3 project [1] which is to provide Component based 
    development for web services. However, Zope interface is also used by other
    web development framework such as Twisted and it is the primary reason for 
    delivery of zope interface here.

    Interfaces are objects that re-specify the external behavior of objects 
that 
    provides them in the first place. An interface can redefine the behavior of
    the original objects through:

    - Replacing a string in the the documentation
    - Modifying the object's attributes.
    - Invariants which is to place conditions that the original objects must
      satisfy.

    Interface support is an important Object Oriented techniques that allows:
    - less patching to the original classes
    - Interfaces can be maintained and yet its implementation can be modified
      to new requirements.
    - modification of GUI without de-stabilizing the applications.
    
    Good examples for how use the zope interface can be found here [2].

    4.2. Bug/RFE Number(s):

        None.

    4.3. In Scope:

        See above.

    4.4. Out of Scope:

        See above.

    4.5. Interfaces:

        --------------------------------------------------------------------
        Exported                        Stability       Comments                
        --------------------------------------------------------------------
        SUNWpython-zope-interface       Uncommitted     Package name
        zope.interface                  Uncommitted     Python module
        zope.interface.adapter          Uncommitted     Python module
        zope.interface.advice           Uncommitted     Python module
        zope.interface.declarations     Uncommitted     Python module
        zope.interface.document         Uncommitted     Python module
        zope.interface.exceptions       Uncommitted     Python module
        zope.interface.interface        Uncommitted     Python module
        zope.interface.interfaces       Uncommitted     Python module
        zope.interface.ro               Uncommitted     Python module
        zope.interface.verify           Uncommitted     Python module
        zope.interface.common           Uncommitted     Python module
        zope.interface.common.idatetime Uncommitted     Python module
        zope.interface.common.interfacesUncommitted     Python module
        zope.interface.common.mapping   Uncommitted     Python module
        zope.interface.common.sequence  Uncommitted     Python module           
        
                                                                            
                                                                            
        --------------------------------------------------------------------
        Imported                        Stability       Comments                
        --------------------------------------------------------------------  
        Python 2.4.x                    Contracted      PSARC 2005/532
                                        External
        

    4.6. Doc Impact:

        Man page will be provided pointing to the on-line API documentation.

    4.7. Admin/Config Impact:

        None.

    4.8. HA Impact:

        None.

    4.9. I18N/L10N Impact:

        The JDS team and the G11N are working together to evaluation and
        provide I18N/L10N support.

    4.10. Packaging & Delivery:
    
        Adds new package, SUNWpython-zope-interface, approx 800K
        Package will go into SUNWCall, SUNWCXall and SUNWCprog clusters.

    4.11. Security Impact:

        None.

    4.12. Dependencies:

        The following versions of the imported interfaces are required:
        Python                  >= 2.4

5. Reference Documents:

    [1] Zope 3 Wiki http://wiki.zope.org/zope3/Zope3Wiki

    [2] README in /usr/lib/python2.4/vendor-packages/zope/interface/README.txt
   




Reply via email to