Any plans for polishing the source code of Clone Digger?

[zpcspm]

I've just run pylint on Clone Digger and it gave me a 40 KB log file.
There are a lot of not-so-important warnings like "missing docstring"
and "line too long", but I guess these should be solved anyway before
proceeding to more complicating refactorings like getting rid of
inline functions and classes.

[Peter Bulychev]

It's a good idea.

Tomorrow or on Monday I'll take a look on the pylint report.

2008/9/12 zpcspm <zpc...@gmail.com>

--
Best regards,
Peter Bulychev.

[Peter Bulychev]

Hi.

I've observed the pylint report. Many things to do.
I don't know when I'll do polishing, but I put it to my todo list.

2008/9/13 Peter Bulychev <peter.b...@gmail.com>

[zpcspm]

On Sep 15, 4:37 pm, "Peter Bulychev" <peter.bulyc...@gmail.com> wrote:
> Hi.
>
> I've observed the pylint report. Many things to do.
> I don't know when I'll do polishing, but I put it to my todo list.

Not a big problem as long as Clone Digger actually works and its
codebase doesn't grow very fast.
But I would suggest you to start the pylint quest by documenting the
code better.
This will eliminate the "Missing docstring" warnings and will make it
easier for other people to understand how the code works.