fix: replace pyarrow arange with pyarrow array + range

[Adames4]

Summary by CodeRabbit

• Refactor
  • Adjusted internal index array construction; grouping behavior and user-visible functionality remain unchanged.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[gemini-code-assist]

Summary of Changes

Hello @Adames4, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a targeted fix within the ratiopath/tiling/utils.py file. The change updates the mechanism for generating a PyArrow array of integer indices, moving from a direct pa.arange call to using pa.array in conjunction with Python's built-in range function. This modification likely addresses a deprecation warning, a type-checking issue (as indicated by the removed type: ignore comment), or ensures better compatibility with recent PyArrow versions, thereby maintaining the robustness of index generation.

Highlights

• PyArrow Array Creation: The method for creating a PyArrow array of indices has been updated in the _pyarrow_group_indices function. Specifically, pa.arange(0, len(x)) was replaced with pa.array(range(len(x))).

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[coderabbitai]

📝 Walkthrough

Walkthrough

The index construction in _pyarrow_group_indices was changed from pa.arange(0, len(x)) to pa.array(range(len(x)), type=pa.int32()); grouping logic and returned groups remain unchanged.

Changes

Cohort / File(s)	Summary
Index Array Construction ratiopath/tiling/utils.py	Replaced pa.arange(0, len(x)) with pa.array(range(len(x)), type=pa.int32()) when building full_indices in _pyarrow_group_indices.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 A small hop in code, a gentle swap,
From arange to array I softly hop,
Indices kept, groups still play,
Tiny change, the same ballet. 🥕✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the specific technical change made in the pull request: replacing pa.arange() with pa.array(range()) in the _pyarrow_group_indices function.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Code Review

This pull request correctly replaces the deprecated pyarrow.arange function with the recommended pyarrow.array(range(...)). This change ensures compatibility with recent versions of the PyArrow library where arange has been removed, and it also cleans up the code by removing a type: ignore comment. The fix is straightforward and well-executed.

[Copilot]

Pull request overview

This PR fixes a compatibility issue by replacing the undocumented pa.arange function with the standard PyArrow API pa.array(range()).

Changes:

• Replaced pa.arange(0, len(x)) with pa.array(range(len(x))) in the _pyarrow_group_indices function
• Removed the type: ignore [attr-defined] comment that was masking the fact that pa.arange is not a documented PyArrow attribute

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.