rapidsai/cudf

`RangeIndex.to_numpy`: Restore caching and fix signature

Closed

#21,347 opened on Feb 5, 2026

View on GitHubContributor guide
 (3 comments) (0 reactions) (0 assignees)C++ (735 forks)batch import
Pythongood first issueimprovement

Repository metrics

Stars
 (6,000 stars)
PR merge metrics
 (Avg merge 17d 21h) (230 merged PRs in 30d)

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

Research direction
Review the current RangeIndex.to numpy implementation in cuDF, compare with pandas signature, and add caching similar to the old values host mechanism.
Tech stack
python
Domain
data
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitPythonpandas
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65