From johnf@sac.sfbay.sun.com Fri Sep 25 16:29:23 2009
Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n8PNTMoO025994
	for <LSARC-ext@sac.sfbay.sun.com>; Fri, 25 Sep 2009 16:29:23 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n8PNTJN4011841;
	Sat, 26 Sep 2009 07:29:21 +0800 (SGT)
Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by
 nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KQJ00D01VWWXI00@nwk-avmta-2.sfbay.sun.com>; Fri,
 25 Sep 2009 16:29:20 -0700 (PDT)
Received: from dm-sfbay-02.sfbay.sun.com ([129.146.11.31])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KQJ007IUVWW8H80@nwk-avmta-2.sfbay.sun.com>; Fri,
 25 Sep 2009 16:29:20 -0700 (PDT)
Received: from sac.sfbay.sun.com (sac.SFBay.Sun.COM [129.146.226.132])
	by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2)
 with ESMTP id n8PNTI4e064586; Fri, 25 Sep 2009 16:29:18 -0700 (PDT)
Received: from sac.sfbay.sun.com (localhost [127.0.0.1])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n8PNTGNs025989; Fri,
 25 Sep 2009 16:29:16 -0700 (PDT)
Received: (from johnf@localhost)
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id n8PNTGAx025985; Fri,
 25 Sep 2009 16:29:16 -0700 (PDT)
Date: Fri, 25 Sep 2009 16:29:16 -0700 (PDT)
From: John Fischer <johnf@sac.sfbay.sun.com>
Subject: Package creation for SQLAlchemy [LSARC/2009/518 FastTrack timeout
 10/02/2009]
To: LSARC-ext@sun.com
Cc: shweta.phabba@sun.com
Message-id: <200909252329.n8PNTGAx025985@sac.sfbay.sun.com>
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
Status: RO
Content-Length: 8454


Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
This information is Copyright 2009 Sun Microsystems
1. Introduction
    1.1. Project/Component Working Name:
	 Package creation for SQLAlchemy
    1.2. Name of Document Author/Supplier:
	 Author:  Shweta Phabba
    1.3  Date of This Document:
	25 September, 2009
4. Technical Description
===============================================
ARC PROPOSAL FOR SUNWblacs Package Porting
===============================================


1 . Introduction
    ------------
  
   1.1 Project Working Name :  
       Package creation for SQLAlchemy
       (SQL toolkit and Object Relational Mapper for Python)

   1.2 Name Of  Document Author :
       Shweta Phabba (shweta.phabba@sun.com)

   1.3 Date Of this Document :
       Aug 17 2009

   1.3.1.Project started on 10th August  

   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 Sponserer For SUNWblacs : 
   1.4.3 Name Of Business unit   : Systems 
   1.4.4 Team Name               : Sun Grid Engine & HPC 	

   1.5 Email Aliases :
   1.5.1 Responsible Manager  :  manjunath.basappa@sun.com
   1.5.2 Responsible Engineer :  shweta.phabba@sun.com


 
2.  Project Summary
    ---------------

    2.1 Project Description  :

        The SQLAlchemy SQL Toolkit and Object Relational Mapper is a comprehensive
        set of tools for working with databases and Python. It has several distinct
        areas of functionality which can be used individually or combined together.
        Its major API components, all public-facing, are illustrated below:

        +-----------------------------------------------------------+
        |             Object Relational Mapper (ORM)                |
        +-----------------------------------------------------------+
        +---------+ +------------------------------------+ +--------+
        |         | |       SQL Expression Language      | |        |
        |         | +------------------------------------+ |        |
        |         +-----------------------+ +--------------+        |
        |         | Dialect/Execution     | |    Schema Management  |
        +---------------------------------+ +-----------------------+
        +----------------------+ +----------------------------------+
        |  Connection Pooling  | |              Types               |
        +----------------------+ +----------------------------------+

       Above, the two most significant front-facing portions of SQLAlchemy are the
       Object Relational Mapper and the SQL Expression Language. These are two
       separate toolkits, one building off the other. SQL Expressions can be used
       independently of the ORM. When using the ORM, the SQL Expression language is
       used to establish object-relational configurations as well as in querying.
    
    

    2.2 Risks And Assumptions :

        Assumptions:
        1. SUNWPython
           SUNWmysql-python
	   SUNWpysqlite
	   SUNWpython-setuptools
           Should be available on system Generally it comes with Opensolaris 
           default installation.

        
3.Technical Description :
  ----------------------- 

   3.1 Technical Description For SQLAlchemy

       ( Using SQLAlcehmy 0.5.5 ) 
         =======================  

       1. SQLAlchemy is an SQL database abstraction library for Python.
	SQLAlchemy provides a full suite of well known enterprise-level
	persistence patterns, designed for efficient and high-performing
	database access, adapted into a simple and Pythonic domain language.

	2. Extremely easy to use for all the basic tasks, such as: accessing
	thread-safe and pooled connections, constructing SQL from Python
        expressions, finding object instances, and commiting object
        modifications back to the database.

        3. Powerful enough for complicated tasks, such as: eager load a graph
	of objects and their dependencies via joins; map recursive adjacency
        structures automatically; map objects to not just tables but to any
        arbitrary join or select statement; combine multiple tables together
        to load whole sets of otherwise unrelated objects from a single
        result set; commit entire graphs of object changes in one step.

	4.Built to conform to what DBAs demand, including the ability to swap
	out generated SQL with hand-optimized statements, full usage of bind
	parameters for all literal values, fully transactionalized and
	consistent updates using Unit of Work.

 	5.Modular. Different parts of SQLAlchemy can be used independently of
        the rest, including the connection pool, SQL construction, and
        ORM. SQLAlchemy is constructed in an open style that allows plenty of
        customization, with an architecture that supports custom datatypes,
        custom SQL extensions, and ORM plugins which can augment or extend
        mapping functionality.   

   3.2 Information About SQLALchemy

       1. Written in Python.
       2. Supports Many Databases as MySQL,SQLite,postgres,Oracle,Firebird,
          Sybase,MS-Access etc.
       3. With ORM This produces the maxiumum efficiency and transaction safety,  
          and minimizes chances of deadlocks.
       4. Function-based query construction allows SQL clauses to be built via 
          Python functions and expressions.
       5. Database mapping and class design are totally separate.
       6. Whole graphs of related objects can often be loaded with a single query 
          that is automatically generated to join the appropriate tables together, 
          known as eager loading.
       7. Composite Primary Key .
       8. Explicit support is available for single-table, concrete-table, and 
          joined table inheritance. Polymorphic loading (that is, a query that 
          returns objects of multple descendant types) is supported for all three 
          styles.
       9. Pre  and post procesing of data.


   3.3 Security Impact:
        
       None.


   3.4. Interfaces:

        Exported Interface

SUNWsqlalchemy python library will be ported to /usr/lib/python2.6
as well as /usr/lib/python3.0

Interface                               Classification    Comments
-----------                            ---------------    ---------- 
SUNWsqlalchemy                          Uncommited        Package Name 
/usr/lib/python2.6/vendor-packages/     Uncommited        Directory For sqlalchemy  
  sqlalchemy                                              library      
/usr/lib/python2.6/vendor-packages/	Uncommited	  Directory for 	
  SQLAlchemy.egg-info                                     sqlalchemy library
/usr/lib/python2.6/vendor-packages/     Uncommited        Object relational mapping 
  sqlalchemy/orm                                          library directory.
/usr/lib/python2.6/vendor-packages/     Uncommited        
  sqlalchemy/ext 
/usr/lib/python2.6/vendor-packages/     Uncommited        
  sqlalchemy/engine
/usr/lib/python2.6/vendor-packages/     Uncommited        
  sqlalchemy/sql
/usr/lib/python2.6/vendor-packages/     Uncommited        Directory for different 
  sqlalchemy/databases                                    database support by 
                                                          sqlalchemy
/usr/lib/python2.6/vendor-packages/    Uncommited         Directory for sqlalchemy
  sqlalchemy/SQLAlchemy.egg-info                                           

And all above mentioned directories will have python libray files .


Imported Interfaces
Interface                           Classification   Comments
----------------                   ---------------  ----------------
SUNWPython                         Commited          LSARC/2005/734
SUNWmysql-python                   Commited          PSARC/2008/081
SUNWpysqlite                       Commited          LSARC/2009/203
SUNWpython-setuptools              Commited          LSARC/2008/207 


4. Resources and Schedule: 
   ----------------------- 

    4.1 Product Approval Committee requested information : 
          
    4.1.1 Consolidation or Prject Name :SFW / SUNWsqlalchemy
    4.1.2 Type of CPT Review and Approval expected :   FastTrack
    4.1.3 ARC review type  :   FastTrack

6. Resources and Schedule
    6.4. Steering Committee requested information
   	6.4.1. Consolidation C-team Name:
		SFW
    6.5. ARC review type: FastTrack
    6.6. ARC Exposure: open


From John.Fischer@Sun.COM Fri Sep 25 16:48:34 2009
Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n8PNmY77027290
	for <LSARC-ext@sac.sfbay.sun.com>; Fri, 25 Sep 2009 16:48:34 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by sunmail3mpk.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id n8PNmXRa022470
	for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Fri, 25 Sep 2009 16:48:34 -0700 (PDT)
Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by
 brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KQJ00F05WSXR000@brm-avmta-1.central.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Fri, 25 Sep 2009 17:48:33 -0600 (MDT)
Received: from brmea-mail-4.sun.com ([192.18.98.36])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KQJ005YBWSWVN40@brm-avmta-1.central.sun.com> for
 LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Fri,
 25 Sep 2009 17:48:32 -0600 (MDT)
Received: from fe-amer-10.sun.com ([192.18.109.80])
	by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n8PNmWwY003429	for
 <LSARC-ext@sun.com>; Fri, 25 Sep 2009 23:48:32 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul  2 2009))
 id <0KQJ00200WQTO300@mail-amer.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Fri, 25 Sep 2009 17:48:32 -0600 (MDT)
Received: from [192.168.10.6] ([unknown] [76.20.56.47])
 by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit
 (built Jul  2 2009)) with ESMTPSA id <0KQJ0055ZWSVG060@mail-amer.sun.com> for
 LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Fri,
 25 Sep 2009 17:48:32 -0600 (MDT)
Date: Fri, 25 Sep 2009 16:45:53 -0700
From: John Fischer <John.Fischer@Sun.COM>
Subject: LSARC/2009/518 - Package creation for SQLAlchemy
Sender: John.Fischer@Sun.COM
To: shweta phabba <Shweta.Phabba@Sun.COM>, LSARC-ext@Sun.COM
Reply-to: John.Fischer@Sun.COM
Message-id: <4ABD5631.70408@sun.com>
MIME-version: 1.0
Content-type: multipart/mixed; boundary="Boundary_(ID_mDu3e883j+sAYr1H9sRLeQ)"
X-PMX-Version: 5.4.1.325704
User-Agent: Thunderbird 2.0.0.22 (X11/20090818)
Status: RO
Content-Length: 8683

This is a multi-part message in MIME format.

--Boundary_(ID_mDu3e883j+sAYr1H9sRLeQ)
Content-type: text/plain; CHARSET=US-ASCII; format=flowed
Content-transfer-encoding: 7BIT

LSARC,

I am sponsoring this case for Shweta Phabba.  I have set the timer for
Friday, October 2nd, 2009.  The case directory contains this proposal.

This project proposes to integrate a set of Python tools call SQLAlchemy
SQL Toolkit and Object Relational Mapper into a Minor release of 
Solaris.  The interfaces are all being classified as Uncommitted.

Thanks,

John

--Boundary_(ID_mDu3e883j+sAYr1H9sRLeQ)
Content-type: text/plain; name=proposal.txt
Content-transfer-encoding: 7BIT
Content-disposition: inline; filename=proposal.txt

===============================================
ARC PROPOSAL FOR SUNWblacs Package Porting
===============================================


1 . Introduction
    ------------
  
   1.1 Project Working Name :  
       Package creation for SQLAlchemy
       (SQL toolkit and Object Relational Mapper for Python)

   1.2 Name Of  Document Author :
       Shweta Phabba (shweta.phabba@sun.com)

   1.3 Date Of this Document :
       Aug 17 2009

   1.3.1.Project started on 10th August  

   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 Sponserer For SUNWblacs : 
   1.4.3 Name Of Business unit   : Systems 
   1.4.4 Team Name               : Sun Grid Engine & HPC 	

   1.5 Email Aliases :
   1.5.1 Responsible Manager  :  manjunath.basappa@sun.com
   1.5.2 Responsible Engineer :  shweta.phabba@sun.com


 
2.  Project Summary
    ---------------

    2.1 Project Description  :

        The SQLAlchemy SQL Toolkit and Object Relational Mapper is a comprehensive
        set of tools for working with databases and Python. It has several distinct
        areas of functionality which can be used individually or combined together.
        Its major API components, all public-facing, are illustrated below:

        +-----------------------------------------------------------+
        |             Object Relational Mapper (ORM)                |
        +-----------------------------------------------------------+
        +---------+ +------------------------------------+ +--------+
        |         | |       SQL Expression Language      | |        |
        |         | +------------------------------------+ |        |
        |         +-----------------------+ +--------------+        |
        |         | Dialect/Execution     | |    Schema Management  |
        +---------------------------------+ +-----------------------+
        +----------------------+ +----------------------------------+
        |  Connection Pooling  | |              Types               |
        +----------------------+ +----------------------------------+

       Above, the two most significant front-facing portions of SQLAlchemy are the
       Object Relational Mapper and the SQL Expression Language. These are two
       separate toolkits, one building off the other. SQL Expressions can be used
       independently of the ORM. When using the ORM, the SQL Expression language is
       used to establish object-relational configurations as well as in querying.
    
    

    2.2 Risks And Assumptions :

        Assumptions:
        1. SUNWPython
           SUNWmysql-python
	   SUNWpysqlite
	   SUNWpython-setuptools
           Should be available on system Generally it comes with Opensolaris 
           default installation.

        
3.Technical Description :
  ----------------------- 

   3.1 Technical Description For SQLAlchemy

       ( Using SQLAlcehmy 0.5.5 ) 
         =======================  

       1. SQLAlchemy is an SQL database abstraction library for Python.
	SQLAlchemy provides a full suite of well known enterprise-level
	persistence patterns, designed for efficient and high-performing
	database access, adapted into a simple and Pythonic domain language.

	2. Extremely easy to use for all the basic tasks, such as: accessing
	thread-safe and pooled connections, constructing SQL from Python
        expressions, finding object instances, and commiting object
        modifications back to the database.

        3. Powerful enough for complicated tasks, such as: eager load a graph
	of objects and their dependencies via joins; map recursive adjacency
        structures automatically; map objects to not just tables but to any
        arbitrary join or select statement; combine multiple tables together
        to load whole sets of otherwise unrelated objects from a single
        result set; commit entire graphs of object changes in one step.

	4.Built to conform to what DBAs demand, including the ability to swap
	out generated SQL with hand-optimized statements, full usage of bind
	parameters for all literal values, fully transactionalized and
	consistent updates using Unit of Work.

 	5.Modular. Different parts of SQLAlchemy can be used independently of
        the rest, including the connection pool, SQL construction, and
        ORM. SQLAlchemy is constructed in an open style that allows plenty of
        customization, with an architecture that supports custom datatypes,
        custom SQL extensions, and ORM plugins which can augment or extend
        mapping functionality.   

   3.2 Information About SQLALchemy

       1. Written in Python.
       2. Supports Many Databases as MySQL,SQLite,postgres,Oracle,Firebird,
          Sybase,MS-Access etc.
       3. With ORM This produces the maxiumum efficiency and transaction safety,  
          and minimizes chances of deadlocks.
       4. Function-based query construction allows SQL clauses to be built via 
          Python functions and expressions.
       5. Database mapping and class design are totally separate.
       6. Whole graphs of related objects can often be loaded with a single query 
          that is automatically generated to join the appropriate tables together, 
          known as eager loading.
       7. Composite Primary Key .
       8. Explicit support is available for single-table, concrete-table, and 
          joined table inheritance. Polymorphic loading (that is, a query that 
          returns objects of multple descendant types) is supported for all three 
          styles.
       9. Pre  and post procesing of data.


   3.3 Security Impact:
        
       None.


   3.4. Interfaces:

        Exported Interface

SUNWsqlalchemy python library will be ported to /usr/lib/python2.6
as well as /usr/lib/python3.0

Interface                               Classification    Comments
-----------                            ---------------    ---------- 
SUNWsqlalchemy                          Uncommited        Package Name 
/usr/lib/python2.6/vendor-packages/     Uncommited        Directory For sqlalchemy  
  sqlalchemy                                              library      
/usr/lib/python2.6/vendor-packages/	Uncommited	  Directory for 	
  SQLAlchemy.egg-info                                     sqlalchemy library
/usr/lib/python2.6/vendor-packages/     Uncommited        Object relational mapping 
  sqlalchemy/orm                                          library directory.
/usr/lib/python2.6/vendor-packages/     Uncommited        
  sqlalchemy/ext 
/usr/lib/python2.6/vendor-packages/     Uncommited        
  sqlalchemy/engine
/usr/lib/python2.6/vendor-packages/     Uncommited        
  sqlalchemy/sql
/usr/lib/python2.6/vendor-packages/     Uncommited        Directory for different 
  sqlalchemy/databases                                    database support by 
                                                          sqlalchemy
/usr/lib/python2.6/vendor-packages/    Uncommited         Directory for sqlalchemy
  sqlalchemy/SQLAlchemy.egg-info                                           

And all above mentioned directories will have python libray files .


Imported Interfaces
Interface                           Classification   Comments
----------------                   ---------------  ----------------
SUNWPython                         Commited          LSARC/2005/734
SUNWmysql-python                   Commited          PSARC/2008/081
SUNWpysqlite                       Commited          LSARC/2009/203
SUNWpython-setuptools              Commited          LSARC/2008/207 


4. Resources and Schedule: 
   ----------------------- 

    4.1 Product Approval Committee requested information : 
          
    4.1.1 Consolidation or Prject Name :SFW / SUNWsqlalchemy
    4.1.2 Type of CPT Review and Approval expected :   FastTrack
    4.1.3 ARC review type  :   FastTrack

--Boundary_(ID_mDu3e883j+sAYr1H9sRLeQ)--

From storycrafter@gmail.com Tue Sep 29 07:53:10 2009
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n8TEr84r000749
	for <LSARC-ext@sac.sfbay.sun.com>; Tue, 29 Sep 2009 07:53:09 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n8TEqG57025226;
	Tue, 29 Sep 2009 15:53:04 +0100 (BST)
Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by
 nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KQQ00M0BMODD400@nwk-avmta-2.sfbay.sun.com>; Tue,
 29 Sep 2009 07:53:01 -0700 (PDT)
Received: from brmea-mail-4.sun.com ([192.18.98.36])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KQQ00IISMOCKZ80@nwk-avmta-2.sfbay.sun.com>; Tue,
 29 Sep 2009 07:53:00 -0700 (PDT)
Received: from relay14i.sun.com
 (ip124.net129179-4.block1.us.syntegra.com [129.179.4.124])
	by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n8TEcPMg029276; Tue,
 29 Sep 2009 14:52:59 +0000 (GMT)
Received: from mmp14es.mmp.us.syntegra.com ([160.41.208.14] [160.41.208.14])
 by relay14i.sun.com with ESMTP id BT-MMP-2898484; Tue,
 29 Sep 2009 14:52:59 +0000 (Z)
Received: from relay14i.sun.com (relay14i.sun.com [129.179.4.124])
 by mmp14es.mmp.us.syntegra.com with ESMTP id BT-MMP-647927; Tue,
 29 Sep 2009 14:52:59 +0000 (Z)
Received: from mail-vw0-f177.google.com ([209.85.212.177] [209.85.212.177])
 by relay1i.sun.com with ESMTP id BT-MMP-12643114; Tue,
 29 Sep 2009 14:52:59 +0000 (Z)
Received: by vws7 with SMTP id 7so3117724vws.17 for <multiple recipients>; Tue,
 29 Sep 2009 07:52:56 -0700 (PDT)
Received: by 10.220.106.230 with SMTP id y38mr7982587vco.43.1254235976211; Tue,
 29 Sep 2009 07:52:56 -0700 (PDT)
Date: Tue, 29 Sep 2009 09:52:56 -0500
From: Mark Martin <storycrafter@gmail.com>
Subject: Re: LSARC/2009/518 - Package creation for SQLAlchemy
In-reply-to: <4ABD5631.70408@sun.com>
To: shweta phabba <Shweta.Phabba@sun.com>
Cc: LSARC-ext@sun.com, John.Fischer@sun.com
Message-id: <e40c28290909290752s30c29df4h8a54b16e370f24a6@mail.gmail.com>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=gmail.com;
 s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references
 :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding;
 bh=jY8N+w1tiFn+L2qNA1e+63JDhTMwNQ8LKJIwJV3mxZk=;
 b=p3TBy80LaTbbCVlSQYtU/MeT3GeSTLfEfd18Rv1QFDQqp6/136PqlaqUgOoSHSrjAq
 9GAIZNxFdah9DknNvCTmjwd2rA5UdErfVF92Ip7nwwMBOR38s5c4/7qDwLutsqsQElsU
 KoWleWPUt1imY0MDyHIabudCynnhfHt2jomEY=
DomainKey-Signature: a=rsa-sha1; c=nofws;        d=gmail.com; s=gamma;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type:content-transfer-encoding;
 b=VnvtFp/hJZNIK0skX0mY8dr+7mpEdas6rsuAg1Xy06Vxar/EFQoLvr5h6T6I/QsQT9
 cUfHIiLJsP+52HjrtKviqaVfOc+6Y1fcnKUR6Nv8r75gnXF4HFSaHuGTRHBIMbbx7R3Z
 woG1mkNb45s+r544ixsEUrTNkj6L7wHis07nM=
X-PMX-Version: 5.4.1.325704
X-Brightmail-Tracker: AAAAAA==
References: <4ABD5631.70408@sun.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by sac.sfbay.sun.com id n8TEr84r000749
Status: RO
Content-Length: 1879

On Fri, Sep 25, 2009 at 6:45 PM, John Fischer <John.Fischer@sun.com> wrote:
>
>   3.4. Interfaces:
>
>        Exported Interface
>
> SUNWsqlalchemy python library will be ported to /usr/lib/python2.6
> as well as /usr/lib/python3.0
>
> Interface                               Classification    Comments
> -----------                            ---------------    ----------
> SUNWsqlalchemy                          Uncommited        Package Name
> /usr/lib/python2.6/vendor-packages/     Uncommited        Directory For
> sqlalchemy
>  sqlalchemy                                              library
> /usr/lib/python2.6/vendor-packages/     Uncommited        Directory for
>  SQLAlchemy.egg-info                                     sqlalchemy library
> /usr/lib/python2.6/vendor-packages/     Uncommited        Object relational
> mapping
>  sqlalchemy/orm                                          library directory.
> /usr/lib/python2.6/vendor-packages/     Uncommited
>  sqlalchemy/ext
> /usr/lib/python2.6/vendor-packages/     Uncommited
>  sqlalchemy/engine
> /usr/lib/python2.6/vendor-packages/     Uncommited
>  sqlalchemy/sql
> /usr/lib/python2.6/vendor-packages/     Uncommited        Directory for
> different
>  sqlalchemy/databases                                    database support by
>                                                          sqlalchemy
> /usr/lib/python2.6/vendor-packages/    Uncommited         Directory for
> sqlalchemy
>  sqlalchemy/SQLAlchemy.egg-info
>
> And all above mentioned directories will have python libray files .
>

(Probably) minor nit -- If you've gone through the trouble of listing
the python2.6 dirs, you may want to list the python3.0 dirs.  Or maybe
s/python2.6/${PYTHON} and briefly define ${PYTHON} below... -- much
like we do with ${MACH64}.


Having said that, this case looks fine to me (and I'm glad to see it!)
+1


From John.Fischer@sun.com Tue Sep 29 15:54:00 2009
Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n8TMs0Re019161
	for <LSARC-ext@sac.sfbay.sun.com>; Tue, 29 Sep 2009 15:54:00 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n8TMrxDU058136
	for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Tue, 29 Sep 2009 16:54:00 -0600 (MDT)
Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by
 brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KQR0070N8XZVA00@brm-avmta-1.central.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Tue, 29 Sep 2009 16:53:59 -0600 (MDT)
Received: from brmea-mail-4.sun.com ([192.18.98.36])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KQR00KT68XZVFB0@brm-avmta-1.central.sun.com> for
 LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Tue,
 29 Sep 2009 16:53:59 -0600 (MDT)
Received: from fe-amer-10.sun.com ([192.18.109.80])
	by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n8TMrxgG011906	for
 <LSARC-ext@sun.com>; Tue, 29 Sep 2009 22:53:59 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul  2 2009))
 id <0KQR00M008UA1G00@mail-amer.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Tue, 29 Sep 2009 16:53:59 -0600 (MDT)
Received: from [192.168.10.5] ([unknown] [76.20.56.47])
 by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit
 (built Jul  2 2009)) with ESMTPSA id <0KQR00D9N8XMYND0@mail-amer.sun.com> for
 LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Tue,
 29 Sep 2009 16:53:47 -0600 (MDT)
Date: Tue, 29 Sep 2009 15:51:06 -0700
From: John Fischer <John.Fischer@sun.com>
Subject: Re: LSARC/2009/518 - Package creation for SQLAlchemy
In-reply-to: <e40c28290909290752s30c29df4h8a54b16e370f24a6@mail.gmail.com>
Sender: John.Fischer@sun.com
To: Mark Martin <storycrafter@gmail.com>
Cc: shweta phabba <Shweta.Phabba@sun.com>, LSARC-ext@sun.com
Reply-to: John.Fischer@sun.com
Message-id: <4AC28F5A.9060400@sun.com>
MIME-version: 1.0
Content-type: text/plain; CHARSET=US-ASCII; format=flowed
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <4ABD5631.70408@sun.com>
 <e40c28290909290752s30c29df4h8a54b16e370f24a6@mail.gmail.com>
User-Agent: Thunderbird 2.0.0.22 (X11/20090818)
Status: RO
Content-Length: 2014

All,

This project was approved today at LSARC.

Thanks,

John


Mark Martin wrote:
> On Fri, Sep 25, 2009 at 6:45 PM, John Fischer <John.Fischer@sun.com> wrote:
>>   3.4. Interfaces:
>>
>>        Exported Interface
>>
>> SUNWsqlalchemy python library will be ported to /usr/lib/python2.6
>> as well as /usr/lib/python3.0
>>
>> Interface                               Classification    Comments
>> -----------                            ---------------    ----------
>> SUNWsqlalchemy                          Uncommited        Package Name
>> /usr/lib/python2.6/vendor-packages/     Uncommited        Directory For
>> sqlalchemy
>>  sqlalchemy                                              library
>> /usr/lib/python2.6/vendor-packages/     Uncommited        Directory for
>>  SQLAlchemy.egg-info                                     sqlalchemy library
>> /usr/lib/python2.6/vendor-packages/     Uncommited        Object relational
>> mapping
>>  sqlalchemy/orm                                          library directory.
>> /usr/lib/python2.6/vendor-packages/     Uncommited
>>  sqlalchemy/ext
>> /usr/lib/python2.6/vendor-packages/     Uncommited
>>  sqlalchemy/engine
>> /usr/lib/python2.6/vendor-packages/     Uncommited
>>  sqlalchemy/sql
>> /usr/lib/python2.6/vendor-packages/     Uncommited        Directory for
>> different
>>  sqlalchemy/databases                                    database support by
>>                                                          sqlalchemy
>> /usr/lib/python2.6/vendor-packages/    Uncommited         Directory for
>> sqlalchemy
>>  sqlalchemy/SQLAlchemy.egg-info
>>
>> And all above mentioned directories will have python libray files .
>>
> 
> (Probably) minor nit -- If you've gone through the trouble of listing
> the python2.6 dirs, you may want to list the python3.0 dirs.  Or maybe
> s/python2.6/${PYTHON} and briefly define ${PYTHON} below... -- much
> like we do with ${MACH64}.
> 
> 
> Having said that, this case looks fine to me (and I'm glad to see it!)
> +1

From Shweta.Phabba@sun.com Tue Sep 29 20:25:01 2009
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n8U3P0VC024609
	for <LSARC-ext@sac.sfbay.sun.com>; Tue, 29 Sep 2009 20:25:00 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n8U3OonY008220
	for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Wed, 30 Sep 2009 04:24:59 +0100 (BST)
Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by
 brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KQR00F07LHL4Q00@brm-avmta-1.central.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Tue, 29 Sep 2009 21:24:57 -0600 (MDT)
Received: from sineb-mail-2.sun.com ([192.18.19.7])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KQR00BWELHJPPB0@brm-avmta-1.central.sun.com> for
 LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Tue,
 29 Sep 2009 21:24:57 -0600 (MDT)
Received: from fe-apac-06.sun.com
 (fe-apac-06.sun.com [192.18.19.177] (may be forged))
	by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n8U3Ot2d015466	for
 <LSARC-ext@sun.com>; Wed, 30 Sep 2009 03:24:55 +0000 (GMT)
Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com
 (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul  2 2009))
 id <0KQR00100LCCEA00@mail-apac.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Wed, 30 Sep 2009 11:24:55 +0800 (SGT)
Received: from [129.158.230.40] ([unknown] [129.158.230.40])
 by mail-apac.sun.com
 (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul  2 2009))
 with ESMTPSA id <0KQR00BVMLHIAB10@mail-apac.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Wed, 30 Sep 2009 11:24:55 +0800 (SGT)
Date: Wed, 30 Sep 2009 08:41:57 +0530
From: shweta phabba <Shweta.Phabba@sun.com>
Subject: Re: LSARC/2009/518 - Package creation for SQLAlchemy
In-reply-to: <4AC28F5A.9060400@sun.com>
Sender: Shweta.Phabba@sun.com
To: John.Fischer@sun.com
Cc: Mark Martin <storycrafter@gmail.com>, LSARC-ext@sun.com
Message-id: <4AC2CC7D.9000603@sun.com>
MIME-version: 1.0
Content-type: text/plain; CHARSET=US-ASCII; format=flowed
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <4ABD5631.70408@sun.com>
 <e40c28290909290752s30c29df4h8a54b16e370f24a6@mail.gmail.com>
 <4AC28F5A.9060400@sun.com>
User-Agent: Thunderbird 2.0.0.4 (X11/20070622)
Status: RO
Content-Length: 2370

hi,
Thanks John For your support in the procedure. One more question i 
wanted to ask you is now i am porting to python 2.6 but you told python 
3.0 also but build machines are not having python 3.0 what to do in this 
case.?

Thanks.


Regards,
Shweta


John Fischer wrote:
> All,
>
> This project was approved today at LSARC.
>
> Thanks,
>
> John
>
>
> Mark Martin wrote:
>> On Fri, Sep 25, 2009 at 6:45 PM, John Fischer <John.Fischer@sun.com> 
>> wrote:
>>>   3.4. Interfaces:
>>>
>>>        Exported Interface
>>>
>>> SUNWsqlalchemy python library will be ported to /usr/lib/python2.6
>>> as well as /usr/lib/python3.0
>>>
>>> Interface                               Classification    Comments
>>> -----------                            ---------------    ----------
>>> SUNWsqlalchemy                          Uncommited        Package Name
>>> /usr/lib/python2.6/vendor-packages/     Uncommited        Directory For
>>> sqlalchemy
>>>  sqlalchemy                                              library
>>> /usr/lib/python2.6/vendor-packages/     Uncommited        Directory for
>>>  SQLAlchemy.egg-info                                     sqlalchemy 
>>> library
>>> /usr/lib/python2.6/vendor-packages/     Uncommited        Object 
>>> relational
>>> mapping
>>>  sqlalchemy/orm                                          library 
>>> directory.
>>> /usr/lib/python2.6/vendor-packages/     Uncommited
>>>  sqlalchemy/ext
>>> /usr/lib/python2.6/vendor-packages/     Uncommited
>>>  sqlalchemy/engine
>>> /usr/lib/python2.6/vendor-packages/     Uncommited
>>>  sqlalchemy/sql
>>> /usr/lib/python2.6/vendor-packages/     Uncommited        Directory for
>>> different
>>>  sqlalchemy/databases                                    database 
>>> support by
>>>                                                          sqlalchemy
>>> /usr/lib/python2.6/vendor-packages/    Uncommited         Directory for
>>> sqlalchemy
>>>  sqlalchemy/SQLAlchemy.egg-info
>>>
>>> And all above mentioned directories will have python libray files .
>>>
>>
>> (Probably) minor nit -- If you've gone through the trouble of listing
>> the python2.6 dirs, you may want to list the python3.0 dirs.  Or maybe
>> s/python2.6/${PYTHON} and briefly define ${PYTHON} below... -- much
>> like we do with ${MACH64}.
>>
>>
>> Having said that, this case looks fine to me (and I'm glad to see it!)
>> +1


From Shweta.Phabba@sun.com Tue Sep 29 20:34:35 2009
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n8U3YXrD024731
	for <LSARC-ext@sac.sfbay.sun.com>; Tue, 29 Sep 2009 20:34:34 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n8U3YT5Y016701
	for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Wed, 30 Sep 2009 04:34:33 +0100 (BST)
Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by
 brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KQR00G03LXJ6500@brm-avmta-1.central.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Tue, 29 Sep 2009 21:34:31 -0600 (MDT)
Received: from sineb-mail-1.sun.com ([192.18.19.6])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KQR00BTVLXIPDB0@brm-avmta-1.central.sun.com> for
 LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Tue,
 29 Sep 2009 21:34:31 -0600 (MDT)
Received: from fe-apac-05.sun.com
 (fe-apac-05.sun.com [192.18.19.176] (may be forged))
	by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n8U3YURT014478	for
 <LSARC-ext@sun.com>; Wed, 30 Sep 2009 03:34:30 +0000 (GMT)
Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com
 (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul  2 2009))
 id <0KQR00K00LOR1R00@mail-apac.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Wed, 30 Sep 2009 11:34:30 +0800 (SGT)
Received: from [129.158.230.40] ([unknown] [129.158.230.40])
 by mail-apac.sun.com
 (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul  2 2009))
 with ESMTPSA id <0KQR009WRLX30060@mail-apac.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Wed, 30 Sep 2009 11:34:15 +0800 (SGT)
Date: Wed, 30 Sep 2009 08:51:18 +0530
From: shweta phabba <Shweta.Phabba@sun.com>
Subject: Re: LSARC/2009/518 - Package creation for SQLAlchemy
In-reply-to: <e40c28290909290752s30c29df4h8a54b16e370f24a6@mail.gmail.com>
Sender: Shweta.Phabba@sun.com
To: Mark Martin <storycrafter@gmail.com>
Cc: LSARC-ext@sun.com, John.Fischer@sun.com
Message-id: <4AC2CEAE.7080903@sun.com>
MIME-version: 1.0
Content-type: text/plain; CHARSET=US-ASCII; format=flowed
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <4ABD5631.70408@sun.com>
 <e40c28290909290752s30c29df4h8a54b16e370f24a6@mail.gmail.com>
User-Agent: Thunderbird 2.0.0.4 (X11/20070622)
Status: RO
Content-Length: 2019

hi,
Thanks  for reviewing the same .

Regards,
Shweta
Mark Martin wrote:
> On Fri, Sep 25, 2009 at 6:45 PM, John Fischer <John.Fischer@sun.com> wrote:
>   
>>   3.4. Interfaces:
>>
>>        Exported Interface
>>
>> SUNWsqlalchemy python library will be ported to /usr/lib/python2.6
>> as well as /usr/lib/python3.0
>>
>> Interface                               Classification    Comments
>> -----------                            ---------------    ----------
>> SUNWsqlalchemy                          Uncommited        Package Name
>> /usr/lib/python2.6/vendor-packages/     Uncommited        Directory For
>> sqlalchemy
>>  sqlalchemy                                              library
>> /usr/lib/python2.6/vendor-packages/     Uncommited        Directory for
>>  SQLAlchemy.egg-info                                     sqlalchemy library
>> /usr/lib/python2.6/vendor-packages/     Uncommited        Object relational
>> mapping
>>  sqlalchemy/orm                                          library directory.
>> /usr/lib/python2.6/vendor-packages/     Uncommited
>>  sqlalchemy/ext
>> /usr/lib/python2.6/vendor-packages/     Uncommited
>>  sqlalchemy/engine
>> /usr/lib/python2.6/vendor-packages/     Uncommited
>>  sqlalchemy/sql
>> /usr/lib/python2.6/vendor-packages/     Uncommited        Directory for
>> different
>>  sqlalchemy/databases                                    database support by
>>                                                          sqlalchemy
>> /usr/lib/python2.6/vendor-packages/    Uncommited         Directory for
>> sqlalchemy
>>  sqlalchemy/SQLAlchemy.egg-info
>>
>> And all above mentioned directories will have python libray files .
>>
>>     
>
> (Probably) minor nit -- If you've gone through the trouble of listing
> the python2.6 dirs, you may want to list the python3.0 dirs.  Or maybe
> s/python2.6/${PYTHON} and briefly define ${PYTHON} below... -- much
> like we do with ${MACH64}.
>
>
> Having said that, this case looks fine to me (and I'm glad to see it!)
> +1
>   


From John.Fischer@sun.com Wed Sep 30 08:20:17 2009
Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n8UFKG77017299
	for <LSARC-ext@sac.sfbay.sun.com>; Wed, 30 Sep 2009 08:20:17 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n8UFKFlL018569
	for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Wed, 30 Sep 2009 23:20:15 +0800 (SGT)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KQS00101ILPAQ00@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Wed, 30 Sep 2009 08:20:13 -0700 (PDT)
Received: from brmea-mail-1.sun.com ([192.18.98.31])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KQS009XBILPU7D0@nwk-avmta-1.sfbay.Sun.COM> for
 LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Wed,
 30 Sep 2009 08:20:13 -0700 (PDT)
Received: from fe-amer-10.sun.com ([192.18.109.80])
	by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n8UFKCtV029454	for
 <LSARC-ext@sun.com>; Wed, 30 Sep 2009 15:20:12 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul  2 2009))
 id <0KQS00700HE85N00@mail-amer.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Wed, 30 Sep 2009 09:20:12 -0600 (MDT)
Received: from [192.168.10.6] ([unknown] [76.20.56.47])
 by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit
 (built Jul  2 2009)) with ESMTPSA id <0KQS00105ILENI30@mail-amer.sun.com> for
 LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Wed,
 30 Sep 2009 09:20:02 -0600 (MDT)
Date: Wed, 30 Sep 2009 08:17:22 -0700
From: John Fischer <John.Fischer@sun.com>
Subject: Re: LSARC/2009/518 - Package creation for SQLAlchemy
In-reply-to: <4AC2CC7D.9000603@sun.com>
Sender: John.Fischer@sun.com
To: shweta phabba <Shweta.Phabba@sun.com>
Cc: Mark Martin <storycrafter@gmail.com>, LSARC-ext@sun.com
Reply-to: John.Fischer@sun.com
Message-id: <4AC37682.2000001@sun.com>
MIME-version: 1.0
Content-type: text/plain; CHARSET=US-ASCII; format=flowed
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <4ABD5631.70408@sun.com>
 <e40c28290909290752s30c29df4h8a54b16e370f24a6@mail.gmail.com>
 <4AC28F5A.9060400@sun.com> <4AC2CC7D.9000603@sun.com>
User-Agent: Thunderbird 2.0.0.22 (X11/20090818)
Status: RO
Content-Length: 3000

Shweta,

You need to have both python 2.6 and python 3.0 packages ready.  At some
point in time python 2.6 will disappear.  So keep an eye out for python
3.0 to appear within the Solaris / Open Solaris WOS.  This project has
a dependency on it but can deliver the python 2.6 packages at any point
in time.  Once the python 3.0 packages appear then the project needs to
port to it and make another delivery.  You do not need to return for
approval for that new delivery because you are already approved.

Thanks,

John


shweta phabba wrote:
> hi,
> Thanks John For your support in the procedure. One more question i 
> wanted to ask you is now i am porting to python 2.6 but you told python 
> 3.0 also but build machines are not having python 3.0 what to do in this 
> case.?
> 
> Thanks.
> 
> 
> Regards,
> Shweta
> 
> 
> John Fischer wrote:
>> All,
>>
>> This project was approved today at LSARC.
>>
>> Thanks,
>>
>> John
>>
>>
>> Mark Martin wrote:
>>> On Fri, Sep 25, 2009 at 6:45 PM, John Fischer <John.Fischer@sun.com> 
>>> wrote:
>>>>   3.4. Interfaces:
>>>>
>>>>        Exported Interface
>>>>
>>>> SUNWsqlalchemy python library will be ported to /usr/lib/python2.6
>>>> as well as /usr/lib/python3.0
>>>>
>>>> Interface                               Classification    Comments
>>>> -----------                            ---------------    ----------
>>>> SUNWsqlalchemy                          Uncommited        Package Name
>>>> /usr/lib/python2.6/vendor-packages/     Uncommited        Directory For
>>>> sqlalchemy
>>>>  sqlalchemy                                              library
>>>> /usr/lib/python2.6/vendor-packages/     Uncommited        Directory for
>>>>  SQLAlchemy.egg-info                                     sqlalchemy 
>>>> library
>>>> /usr/lib/python2.6/vendor-packages/     Uncommited        Object 
>>>> relational
>>>> mapping
>>>>  sqlalchemy/orm                                          library 
>>>> directory.
>>>> /usr/lib/python2.6/vendor-packages/     Uncommited
>>>>  sqlalchemy/ext
>>>> /usr/lib/python2.6/vendor-packages/     Uncommited
>>>>  sqlalchemy/engine
>>>> /usr/lib/python2.6/vendor-packages/     Uncommited
>>>>  sqlalchemy/sql
>>>> /usr/lib/python2.6/vendor-packages/     Uncommited        Directory for
>>>> different
>>>>  sqlalchemy/databases                                    database 
>>>> support by
>>>>                                                          sqlalchemy
>>>> /usr/lib/python2.6/vendor-packages/    Uncommited         Directory for
>>>> sqlalchemy
>>>>  sqlalchemy/SQLAlchemy.egg-info
>>>>
>>>> And all above mentioned directories will have python libray files .
>>>>
>>>
>>> (Probably) minor nit -- If you've gone through the trouble of listing
>>> the python2.6 dirs, you may want to list the python3.0 dirs.  Or maybe
>>> s/python2.6/${PYTHON} and briefly define ${PYTHON} below... -- much
>>> like we do with ${MACH64}.
>>>
>>>
>>> Having said that, this case looks fine to me (and I'm glad to see it!)
>>> +1
> 

