hi,
Thanks for reviewing the same .
Regards,
Shweta
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
>
