rapidsai/cudf

`RangeIndex.to_numpy`: Restore caching and fix signature

Open

#21347 opened on Feb 5, 2026

View on GitHub
 (3 comments) (0 reactions) (0 assignees)C++ (6,000 stars) (735 forks)batch import
Pythongood first issue

Description

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

Contributor guide

Tech stack
pythoncpp
Domain
dataperformance
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Familiarity with pandas RangeIndex.to numpyUnderstanding of cuDF's values host cachingBasic Python development setup
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
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.