After fixing its version to 0.0.2 (released on 22 May 2023), I observed the following strange behavior:
In refactor-graph-lifting, pytest runs our tests successfully.
In add-new-lifts, TopoNetXs adjacency_matrix() makes scipy raise an error.
I could not locate the source of the issue, but it is resolved when I stop fixing the version to 0.0.2. My guess is that some new updates since the 0.0.2 release may have addressed that problem. If we do not fix the version to 0.0.2, all tests pass.
As @mauriciogtec correctly pointed out, we should eventually fix the version since TopoNetX is under development, but there is currently no viable version to fix to. I suggest keeping this issue open and for now and fix TopoNetX to a specific commit (the main branch is ahead of 0.0.2 by 700+ commits). Once there is a new release/tag, we can fix to that (assuming it does not introduce any issues).
After fixing its version to 0.0.2 (released on 22 May 2023), I observed the following strange behavior:
refactor-graph-lifting,pytestruns our tests successfully.add-new-lifts,TopoNetXsadjacency_matrix()makesscipyraise an error.I could not locate the source of the issue, but it is resolved when I stop fixing the version to 0.0.2. My guess is that some new updates since the 0.0.2 release may have addressed that problem. If we do not fix the version to 0.0.2, all tests pass.
As @mauriciogtec correctly pointed out, we should eventually fix the version since
TopoNetXis under development, but there is currently no viable version to fix to. I suggest keeping this issue open and for now and fixTopoNetXto a specific commit (themainbranch is ahead of0.0.2by 700+ commits). Once there is a new release/tag, we can fix to that (assuming it does not introduce any issues).