Workaround inconsistent naming for marisa-trie by not using wheel

[BlankEclair]

Summary by CodeRabbit

• Chores
  • Enhanced the build pipeline for the Python package. The process now compiles directly from source, ensuring that generated artefacts follow a consistent naming convention without requiring additional renaming.
  • These improvements help deliver more reliable and stable releases for end-users.

[coderabbitai]

Walkthrough

The changes update the GitHub Actions workflow for building the marisa-trie Python wheel. The workflow now uses the --no-binary marisa_trie option to ensure the package is built from source. A comment has been added to explain that this produces the desired file naming convention. Additionally, the wheel renaming step has been removed.

Changes

File(s)	Change Summary
.github/workflows/python.yml	Replaced the original wheel build command with one including --no-binary marisa_trie; added a clarifying comment; removed the wheel renaming command.

Sequence Diagram(s)

sequenceDiagram
    participant GHA as GitHub Actions
    participant Pip as pip
    participant Build as Build System

    GHA->>Pip: Execute `pip wheel --no-binary marisa_trie`
    Pip->>Build: Compile marisa-trie from source
    Build-->>Pip: Return the built wheel
    Pip-->>GHA: Deliver the built wheel

Loading

Poem

I’m a bunny with a bounce in my step,
Hopping through code with a clever prep.
Marisa-trie builds from source today,
No binaries to lead my carrots astray.
In GitHub workflows I cheer with delight—
A rabbit’s magical build, oh what a sight!
🐰💻

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.github/workflows/python.yml (1)

47-50: Clarify and Verify the Build Command for marisa-trie:
The updated command now employs the --no-binary marisa_trie option to force building from source, which should yield the desired file naming convention. The accompanying comment explains this rationale; however, the presence of the FIXME tag suggests the workaround is temporary. Consider updating or removing the FIXME tag once the issue is fully resolved. Additionally, verify that this change is compatible with the dependency resolution in your requirements file and produces the expected wheel filename during the build process.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9d1b53e and f926d93.

📒 Files selected for processing (1)

• .github/workflows/python.yml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: deb