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? ;-) > 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. If Tcl/Tk is in fact used to drive the GUI, then what are the GNOME libraries used for? > 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)? -Seb
