Dependency tracking about conda-forge.github.io HOT 18 OPEN

I think it may be possible to use NetworkX for at least the visualization part.

from conda-forge.github.io.

I made a very hackish visualization of conda packages dependencies in the past.

See https://ocefpaf.github.io/python4oceanographers/blog/2014/11/17/networkX/

I am sure you guys can improve upon that 😉

from conda-forge.github.io.

I'd also like to see the packages upon which our feedstocks depend, particularly those which don't themselves have feedstocks.

from conda-forge.github.io.

I could see some other nice use cases as well. Take for instance a package is the dependency of lots of things, but has few maintainers. We could identify this (perhaps with some color coding) and try to encourage people to help support it. Also, it could help identify packages that are not actively supported by anyone.

from conda-forge.github.io.

indeed - that would be a great tool to highlight where to work next. Ideally, the visualization/list could also be platform-specific, since we have many packages that omit some platforms.

from conda-forge.github.io.

Looks like @pelson is coming up with a script to detect missing dependencies in this PR ( #80 ).

It is pretty rudimentary, but gives me some useful information & I wanted to share early.

from conda-forge.github.io.

Think this is to some degree addressed by @CJ-Wright and @justcalamari's work (ref below). Would be good to be able to visualize that graph though. Not sure if either of you have something or ideas along those lines.

ref: https://github.com/regro/cf-scripts

from conda-forge.github.io.

I think that would be a fantastic way to visualise the packages that conda-forge provides. ❤️

from conda-forge.github.io.

Looks like @pelson is coming up with a script to detect missing dependencies in this PR ( #80 ).

from conda-forge.github.io.

See this comment. There is a strategy for doing this at Continuum. We should look and see what changes are required to accommodate that here. Thus far, it doesn't sound so bad.

from conda-forge.github.io.

So there is now feedstockrot thanks to @RSully, which should help.

from conda-forge.github.io.

Also saw this for pip, which is kind of nice. Maybe something worth drawing on.

from conda-forge.github.io.

As far as using networkx, that seems like a good idea, but we still need a package for it ( conda-forge/staged-recipes#1259 ). 😜

from conda-forge.github.io.

Also ran across toposort, which seems pretty handy for planning large scale upgrades. Maybe also helpful in diagnosing where things might have gone wrong during such an upgrade.

from conda-forge.github.io.

Worth mentioning snakefood here.

from conda-forge.github.io.

I will take a stab at the visualization using datashader+holoviews+bokeh similar to how Anaconda did here.

edit: changed link to page instead of notebook

from conda-forge.github.io.

Sound like a good idea. Might also want to take a look at this tutorial. Admittedly Datashader may be needed to get this to work at our scale.

from conda-forge.github.io.

The data for this is in https://github.com/regro/cf-graph-countyfair and https://github.com/regro/libcfgraph

from conda-forge.github.io.