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 at 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
> 

Reply via email to