rapidsai/cudf

[DOC] Split `cudf/source/user_guide/10min.ipynb` into 2 notebooks for cuDF and Dask-cuDF

Open

#21,374 创建于 2026年2月6日

在 GitHub 查看
 (2 评论) (0 反应) (1 负责人)C++ (6,000 star) (735 fork)batch import
docgood first issue

描述

Report incorrect documentation

Location of incorrect documentation cudf/source/user_guide/10min.ipynb

Describe the problems or issues found in the documentation Currently this notebook (and other notebooks that use Dask) isn't being validated in our CI https://github.com/rapidsai/cudf/blob/62387458abe94670c386460a39c877c7530d544d/ci/test_notebooks.sh#L52

And it's likely that https://github.com/rapidsai/cudf/pull/20925 broke something in this notebook when run by-hand.

Suggested fix for documentation

  1. Create 2, 10 minutes to [cuDF|Dask-cuDF] notebooks so we can at least validate a (probably commonly seen) introductory cuDF notebook
  2. Investigate other notebooks that might be running Dask and split them out into other notebooks if appropriate. (The CI currently only skips validating 10min.ipynb because of Dask usage)

贡献者指南

技术栈
python
领域
documentation
议题类型
documentation
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
blocked
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
PythonJupyter
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
40
研究方向
Examine the current notebook at cudf/source/user guide/10min.ipynb to understand its content and structure. Review the CI script at ci/test notebooks.sh to see how notebooks are validated for correct execution. Investigate the changes introduced in PR #20925 that may have broken the notebook when run manually. Create two separate notebooks: one for cuDF only and one for Dask cuDF, and update the CI script to validate both new notebooks.