You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
A breaking change was introduced in 22.06 where the comms dir was moved from cugraph/cugraph/comms to cugraph/cugraph/dask/comms. This affect the way the comms are imported and break prior releases which are still importing the comms the old: way import cugraph.comms as Comms. When attempting to do so, the user would get the error below
import cugraph.comms as Comms
ModuleNotFoundError: No module named 'cugraph.comms'
Ideally we would like to not break our previous releases.
The text was updated successfully, but these errors were encountered:
A breaking change in 22.06 moved the functionalities of `comms` to `cugraph/dask` where it should belong as it is only part of the multi GPU API. However `cugraph/__init__.py` is still importing the the comms when it shouldn't.
This PR removes the `comms` import in `cugraph/__init__.py `
closes#2379closes#2329
Authors:
- Joseph Nke (https://github.com/jnke2016)
Approvers:
- Rick Ratzel (https://github.com/rlratzel)
URL: #2402
Describe the bug
A breaking change was introduced in 22.06 where the
comms
dir was moved fromcugraph/cugraph/comms
tocugraph/cugraph/dask/comms
. This affect the way the comms are imported and break prior releases which are still importing thecomms
the old: wayimport cugraph.comms as Comms
. When attempting to do so, the user would get the error belowIdeally we would like to not break our previous releases.
The text was updated successfully, but these errors were encountered: