@netzschleuder@social.skewed.dejung: JUNG and javax class dependencies (2012)
A network of software class dependency within the JUNG 2.0.1 and javax 1.6.0.7 library namespaces edu.uci.ics.jung and java/javax. Nodes represent classes and a directed edge indicates a dependency of one class on another.
This network has 6120 nodes and 138706 edges.
Tags: Technological, Software, Unweighted
@alexanderadam@ruby.socialUuuh, :ruby: #Ruby will likely get #Namespaces although the syntax will change because #GitLab already uses `Namespace` a lot and @…
@netzschleuder@social.skewed.dejung: JUNG and javax class dependencies (2012)
A network of software class dependency within the JUNG 2.0.1 and javax 1.6.0.7 library namespaces edu.uci.ics.jung and java/javax. Nodes represent classes and a directed edge indicates a dependency of one class on another.
This network has 6120 nodes and 138706 edges.
Tags: Technological, Software, Unweighted
@netzschleuder@social.skewed.dejung: JUNG and javax class dependencies (2012)
A network of software class dependency within the JUNG 2.0.1 and javax 1.6.0.7 library namespaces edu.uci.ics.jung and java/javax. Nodes represent classes and a directed edge indicates a dependency of one class on another.
This network has 6120 nodes and 138706 edges.
Tags: Technological, Software, Unweighted
@netzschleuder@social.skewed.dejung: JUNG and javax class dependencies (2012)
A network of software class dependency within the JUNG 2.0.1 and javax 1.6.0.7 library namespaces edu.uci.ics.jung and java/javax. Nodes represent classes and a directed edge indicates a dependency of one class on another.
This network has 6120 nodes and 138706 edges.
Tags: Technological, Software, Unweighted
@mgorny@social.treehouse.systemsA bad #Python bump morning in #Gentoo:
1. A project that couldn't be bothered to make a release with a security fix for 4 years finally made a release. Of course, if you make one release in 7 years, it is definitely a good idea to replace your build system with a broken #PythonPoetry #setuptools hybrid.
2. Another project made a release with a bunch of test failures — that were fixed in "master" branch already at the time, but I guess nobody bothered testing the release branch.
3. Just discovered that a bunch of projects are using pkg_resources namespaces again — and we were supposed to have gotten rid of them years ago! Of course it's #Google. And on top of that, since pkg_resources are now throwing deprecation warnings, they are indirectly breaking random other test suites.
On the positive side, test_lolwut is failing for me in redis-py.