Ivan Carvalho

> So far all I have done is implement the [modularity](https://networkx.org/documentation/stable/reference/algorithms/generated/networkx.algorithms.community.quality.modularity.html#networkx.algorithms.community.quality.modularity) function (which the Louvain algorithm tries to maximize) in [this branch](https://github.com/jpacold/rustworkx/tree/louvain). > > Before going any further I wanted...

> It seems that the developers of petgraph believe that these community detection algorithms should be offered as a separate package, plz see [petgraph/petgraph#185](https://github.com/petgraph/petgraph/issues/185). However, I’m not sure if their...

Test build: https://github.com/IvanIsCoding/rustworkx/actions/runs/19018757675

I upgraded cibuildwheel 3.3.0. Because of #1527 and #1528 I will need to test the release process again, I think it's fine to merge with only 3.2.1 testing.

This should be trivial to implement with https://www.rustworkx.org/apiref/rustworkx.graph_complement.html We can also leverage an optimized version

I will take a look at this during the weekend. Thanks for sending the fix for an issue you found!

Also, you'll need to solve some minor conflicts with #1510

I think porting our core functionality from `rustworkx-core` is a good effort now that Qiskit's Rust code also depends on us. I also think that it benefits the Rust community...

> I think as we build out `rustworkx-core` to be closer to feature parity with the Python API, it's also a good opportunity to make sure that we're standardizing on...

> * Fixed two mistakes in the modularity gain calculation (I am actually a little surprised that the tests passed earlier and need to come up with some more) >...