[cheesecake-users] pylint curiousness
grig.gheorghiu at gmail.com
Tue Jul 11 09:46:12 PDT 2006
On 7/11/06, will guaraldi <willg at bluesock.org> wrote:
> On Mon, 10 Jul 2006, Grig Gheorghiu wrote:
> > Will,
> > Thanks for reporting this issue. It does seem like the sane approach for
> > cheesecake should be to run pylint on the package as a whole, as opposed
> > to the current way of running it on individual files. We have a
> > pylint-related story coming up soon, so we'll add this task to the
> > story.
> The problem of running it on the entire package at the same time is that
> you don't get the level of granularity you might want (I'm
> hypotheticalizing that's what you want).
> I did some more poking around (i.e. I read the documentation which I
> should have done before) and what pylint does is add the current directory
> to the head of sys.path before checking the module. So if the module is
> deep into a package, then you should run pylint from the top of the
> package. For my specific example, running:
> pylint PyBlosxom/cache/entryshelve.py
> works fine. But running:
> pylint entryshelve.py
> in the Pyblosxom/cache directory doesn't work at all.
> I did an svn update, made some changes, and produced the attached diff
> which fixes the pylint problem I had without resorting to switching to
> pylinting the package all at once.
Cool! Thanks a lot, Will, I'll apply the patch.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cheesecake-users