Re: Bug#510350: ITP: snakefood -- Python dependency grapher
This looks like a very useful application.
On Wed, Dec 31, 2008 at 11:27 AM, Sandro Tosi <firstname.lastname@example.org> wrote:
> * It works on a set of files, i.e. you do not have to specify a
> single script, you can select a directory (package or else) or a
> set of files. It finds all the Python files recursively
> * Automatic/no configuration: your PYTHONPATH is automatically
> adjusted to include the required package roots. It figures out the
> paths that are required from the files/directories given as
> input. You should not have to setup ANYTHING.
> Graphing dependencies always requires the user
> to filter and cluster the filenames, so this is appropriate.
Maybe I'm missing something, but these statements seem inconsistent.
If the user always has to filter the filenames, what does it mean for
it to automatically find the Python files recursively? In what sense
is it automatic? I think you mean something more specific than just
saying the user must always filter "filenames" since it's unclear what
Daniel Moerner <email@example.com>