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.