remove docs dependencies

[jameslamb]

While working on rapidsai/build-planning#155, I realized that this repo no longer has any docs builds.

As far as I can tell, it's just relying on cugraph-docs to build and publish its docs:

• https://github.com/rapidsai/cugraph-docs/tree/branch-25.04/docs/cugraph-docs/source/nx_cugraph

If I'm right about that, then this repo doesn't need any dependencies.yaml entries for sphinx and related dependencies. This proposes removing those, along with other configuration that looks unused (possibly left-over from when this was ported out of https://github.com/rapidsai/cugraph).

Notes for Reviewers

It looks to me likenx-cugraph API docs are missing, maybe unintentionally. Opened rapidsai/cugraph-docs#101 to discuss that.

I think this PR can be merged without a resolution to that conversation... if we want them, we'd likely build those docs with sphinx.ext.autosummary as is done for other Python docs there (example for cugraph).

[copy-pr-bot]

Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually.

Contributors can view more details about this message here.

[jameslamb]

/ok to test

[eriknw]

These changes look good to me. Shall we also remove the docs target from build.sh?

Also, how should we handle docs requests for this repo? Should we accept them here, or point them to cugraph-docs repo? That is, should we update the issue templates docs_request_new.yaml or docs_request_correction.yaml?

[jameslamb]

Shall we also remove the docs target from build.sh?

Good idea! Just did that (and removed a few more places where configuration pointed at the nonexistent docs/ directory) here: 3a6a0f2

should we update the issue templates docs_request_new.yaml or docs_request_correction.yaml?

I think that depends on the outcome of rapidsai/cugraph-docs#101

If that issues goes the way I think it'll go, then nx-cugraph docs will be sourced from 2 places:

• this repo: Python code and its docstrings (for API docs)
• cugraph-docs repo: other long-form docs (and notebooks one day?) (code link)

It's up to you all (and including @acostadon ) what you think will provide the best experience for users and outside contributors.

[eriknw]

Thanks @jameslamb! This was something we were unsure of during the repo migration.

[jameslamb]

/merge