Extracting python dependencies automatically

Michael Schwendt mschwendt.tmp0701.nospam at arcor.de
Wed Aug 15 15:47:02 UTC 2007


On Wed, 15 Aug 2007 18:33:13 +0300 (EEST), Panu Matilainen wrote:

> On Wed, 15 Aug 2007, James Bowes wrote:
> 
> > On Wed, Aug 15, 2007 at 04:51:06PM +0300, Panu Matilainen wrote:
> >>
> >> Started looking into possibilities of extracting python dependency
> >> information similarly to perl dependencies...
> >
> > Cool. This would be nice to have.
> >
> >> For requires, try to locate any python scripts and modules and for each
> >> found, run them through python's modulefinder which attempts to figure out
> >> which modules a script/module uses. Then, based on the filenames gotten
> >> from modulefinder results, turn them into python(<name>) entries, for
> >> example:
> >> [pmatilai at localhost ~]$ rpm -ql createrepo|./pythondeps.py -R
> >> python(_sqlitecache)
> >
> > Something wonky is going on here, I think. Nothing should be importing
> > _sqlitecache besides sqlitecachec, so maybe modulefinder is recursing?
> 
> It shows various indirectly loaded modules as well, because 
> modulefinder loads the modules it looks at and then figures out 
> what files got loaded (or roughly so).
> 
> Should be harmless though...

s/harmless/broken/

It creates dependencies on private modules, which is a problem.
python(rpm._rpmmodule) is wrong, ought to be python(rpm)




More information about the devel mailing list