rapidsai/cudf

`RangeIndex.to_numpy`: Restore caching and fix signature

Open

#21,347 创建于 2026年2月5日

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

描述

Currently, RangeIndex.to_numpy() is missing standard pandas arguments and lacks the caching mechanism previously provided by values_host. We should add caching back and make the signature compliant:

def to_numpy(self, dtype=None, copy=False, na_value=None)
  • See #21346

贡献者指南

技术栈
pythoncpp
领域
dataperformance
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
fresh
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Familiarity with pandas RangeIndex.to numpyUnderstanding of cuDF's values host cachingBasic Python development setup
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
65
研究方向
The contributor should first examine the current implementation of RangeIndex.to numpy in cuDF's Python source, likely in a file like python/cudf/core/index.py or similar. The referenced issue #21346 may provide background on the previously used caching mechanism via values host. To match the standard pandas signature, check the pandas documentation for RangeIndex.to numpy. The fix should add caching back by integrating with the values host mechanism, ensuring the signature includes dtype, copy, and na value parameters. Discussion in the issue comments (if any) may clarify maintainer expectations.