Why isn't pychecker mentioned prominently?

[Michael Hudson]

Pete Shinners <shredwheat at attbi.com> writes:

> Edward K. Ream wrote:
> > I just found out about pychecker (http://pychecker.sourceforge.net/) and
> > I am wondering why it isn't mentioned prominently all over the Python
> > web site: the tutorial, the links on the left and side of the home page,
> > topics guides, general reference etc.  I found out about it from reading
> > one of Guido's recent presentations in which he mentions it as one of
> > his favorite Python tools.  So why is pychecker such a secret?

I think partly because it's fairly new.

> i heartily agree. i now try to use pychecker on absolutely everything
> i do. i really wish it came as part of the standard distribution. it
> could easily be enabled on the commandline with some sort of -wall.
> 
> heck, python recently added the full "warning" framework. it seems
> like an ideal place to tie that all in. then users can control if the
> pychecker warnings were silenced, printed, or treated as exceptions.

I think pychecker integration is a goal of 2.3.  IIRC, one problem is
that pychecker currently works by analysing bytecode, which is totally
unportable to jython.  It would be nicer if it used the compiler
package to work off the syntax tree, but noone's gotten round to
amending it yet.  Patches welcome, I suspect.

now-where's-that-cloning-machine-ly y'rs
m.

-- 
  There are 'infinite' number of developed artifacts and one cannot
  develop appreciation for them all.  It would be all right to not
  understand something, but it would be imbecilic to put judgements
  on things one don't understand.               -- Xah, comp.lang.lisp