A new major version of networkx is out. I have some (external) Python packages that moved to this version. It is backward incompatible, however. https://github.com/networkx/networkx/releases/tag/networkx-2.1
The *major* release 2.0 is from September last year. The *minor* release 2.1 is new, if semver has anything to say about it.
(In reply to Jeroen Roovers from comment #1) > The *major* release 2.0 is from September last year. The *minor* release 2.1 > is new, if semver has anything to say about it. Yes, but 2.1 would be the first from the 2.x series to go into portage, which I thought relevant to stress.
wow, I just finish updating upstream openstack to work with 2.1 (from 1.11) and now I get assigned this bug. spooky
(In reply to Matthew Thode ( prometheanfire ) from comment #3) > wow, I just finish updating upstream openstack to work with 2.1 (from 1.11) > and now I get assigned this bug. spooky Heh, yeah I need it for the next release of app-admin/setools too.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=20183dd27e6de43cdc01daba6fcb0e370a8034bd commit 20183dd27e6de43cdc01daba6fcb0e370a8034bd Author: Matthew Thode <prometheanfire@gentoo.org> AuthorDate: 2018-07-18 19:57:48 +0000 Commit: Matthew Thode <prometheanfire@gentoo.org> CommitDate: 2018-07-18 19:58:37 +0000 dev-python/networkx: 2.1 bup docs need work Closes: https://bugs.gentoo.org/647490 Package-Manager: Portage-2.3.43, Repoman-2.3.10 dev-python/networkx/Manifest | 1 + dev-python/networkx/metadata.xml | 3 ++ dev-python/networkx/networkx-2.1.ebuild | 58 +++++++++++++++++++++++++++++++++ 3 files changed, 62 insertions(+)
