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
Who: end users, cugraph developers
What: Create a new package (cugraph and pip) for users with minimal dependencies needed only for core PG functionality
Why: The new PG implementation will likely have new dependencies not essential to other cugraph use cases, so a separate package benefits users by keeping dependencies for non-PG use cases to a minimum.
Questions:
PG won't (likely) depend on cugraph, but should cugraph depend on PG, perhaps if we want cugraph.Graph to have support for properties like NetworkX Graph?
If PG has a method to extract a cugraph.Graph subgraph, should it have a hard dependency on cugraph? If so, does that remove a major advantage of having PG and cugraph in separate packages (ie. not requiring PG to have all cugraph deps)?
The content you are editing has changed. Please copy your edits and refresh the page.
Who: end users, cugraph developers
What: Create a new package (cugraph and pip) for users with minimal dependencies needed only for core PG functionality
Why: The new PG implementation will likely have new dependencies not essential to other cugraph use cases, so a separate package benefits users by keeping dependencies for non-PG use cases to a minimum.
Questions:
cugraph.Graph
to have support for properties like NetworkX Graph?cugraph.Graph
subgraph, should it have a hard dependency on cugraph? If so, does that remove a major advantage of having PG and cugraph in separate packages (ie. not requiring PG to have all cugraph deps)?Tasks
The text was updated successfully, but these errors were encountered: