Sebastien,

My responses are in-line.  I have included another draft of the proposal 
with edits based on your
comments.

Thanks,

-Erik


Sebastien Roy wrote:
> On Thu, 2009-05-28 at 14:51 -0700, James Walker wrote:
>   
>>      Pylint[1] is a python tool that checks if a Python module satisfies a 
>> coding
>>      standard by analyzing Python source code looking for bugs and signs of
>>      pool quality.
>>     
>
> I'm guessing it looks for signs of poor quality? ;-)
>   
correct :)
>   
>>      pylint-0.18.0 will be integrated into the SFW consolidation
>>         as part of this proposal, and will be installed as SUNWpylint.
>>
>>      This project requests a minor release binding.
>>     
>
> It looks like this project makes no backward incompatible changes to any
> existing software.  As such, Minor binding seems unnecessarily
> restrictive.  Why not Patch?
>
>   
>>      Exported Interfaces                     Classification  Comment
>>      -------------------                     --------------  -------
>>      SUNWpylint                              Uncommitted     Package
>>      /usr/bin/pylint                         Uncommitted     Python script
>>      /usr/bin/symilar                        Uncommitted     Python script
>>      /usr/bin/pyreverse                      Uncommitted     Python script
>>      /usr/bin/epylint                        Uncommitted     Python script
>>      /usr/bin/pylint-gui                     Uncommitted     Python script
>>     
>
> It appears that the project team has supplied man pages for each of
> these interfaces in the materials directory (thank you).  Of note is the
> reference to the use of Tcl/Tk by pylint-gui(1), which suggests that
> there should be some additional related imported interfaces below. 
Tk represents python's standard built in Tkinter interface, not tcl's.
>  If
> Tcl/Tk is in fact used to drive the GUI, then what are the GNOME
> libraries used for?
>   
The Gnome libraries are a requirement for SUNWlogilab-common.  Should we 
leave out
SUNWgnome-libs and SUNWgnome-python-libs as they are covered by the 
dependencies
for SUNWlogilab-common?
>   
>>      Imported Interfaces     Classification  Comment
>>      -------------------     --------------  ---------------------------
>>      SUNWPython              Volatile        Python interpreter, library
>>      SUNWgnome-libs          Volatile        GNOME platform libraries
>>      SUNWgnome-python-libs   Volatile        Python GNOME libraries
>>      SUNWlogilab-common      Uncommitted     Python library
>>      SUNWlogilab-astng       Uncommitted     Python library
>>     
>
> I don't see the latter two packages in the existing repositories.  Are
> they in fact being delivered by this case (and should therefore be part
> of the exported interfaces), or being delivered by a separate case (if
> so there is case dependency that should be called out)?
>   
SUNWlogilab-common and SUNWlogilab-astng are separate cases:
        SUNWlogilab-common          http://sac.sfbay/arc/LSARC/2009/298/   
        SUNWlogilab-astng                
http://sac.sfbay/arc/LSARC/2009/299/
> -Seb
>
>
>   

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: pylint.proposal.txt
URL: 
<http://mail.opensolaris.org/pipermail/opensolaris-arc/attachments/20090529/72d7a1bb/attachment.txt>

Reply via email to