GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — binascii.hexlify by youknowone · Pull Request #5820 · RustPython/RustPython

Conversation

@youknowone

@youknowone youknowone commented Jun 22, 2025 •
edited by coderabbitai Bot
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown
Member

Summary by CodeRabbit

  • New Features

    • Enhanced hexlify functionality to support optional separators between groups of hex-encoded bytes.
  • Bug Fixes

    • Updated test cases to run as normal tests, removing their expected failure status.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
@youknowone
binascii.hexlify
eafdfe1
@coderabbitai

coderabbitai Bot commented Jun 22, 2025 •
edited
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown
Contributor

Walkthrough

The updates enhance the hexlify function in the binascii module to support optional separator insertion between groups of hex-encoded bytes. Corresponding test cases are updated to remove expected failure markers, reflecting the improved functionality. The function and struct signatures are adjusted to accommodate these changes.

Changes

File(s) Change Summary
stdlib/src/binascii.rs Extended hexlify to accept optional separator and interval arguments; updated function and struct signatures.
Lib/test/test_binascii.py Removed @unittest.expectedFailure and related comments from two test methods.

Sequence Diagram(s)

sequenceDiagram
    participant Caller
    participant binascii.hexlify
    participant Validator

    Caller->>binascii.hexlify: Call with data, sep (optional), bytes_per_sep (optional)
    binascii.hexlify->>Validator: Validate sep (if provided)
    Validator-->>binascii.hexlify: Return validation result
    binascii.hexlify->>binascii.hexlify: Hexlify data, insert sep at intervals (if specified)
    binascii.hexlify-->>Caller: Return hexlified bytes (with or without separators)
Loading

Poem

In the land of hex, a new path appears,
With separators dancing between bytey peers.
No longer expected to stumble or fail,
The tests now hop on a seamless trail.
Rusty code and Python unite,
Hexlify shines ever so bright!
🐇✨


📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 5d68313 and eafdfe1.

📒 Files selected for processing (2)
  • Lib/test/test_binascii.py (0 hunks)
  • stdlib/src/binascii.rs (2 hunks)
💤 Files with no reviewable changes (1)
  • Lib/test/test_binascii.py
⏰ Context from checks skipped due to timeout of 90000ms (11)
  • GitHub Check: Run snippets and cpython tests on wasm-wasi
  • GitHub Check: Run snippets and cpython tests (windows-latest)
  • GitHub Check: Run tests under miri
  • GitHub Check: Check the WASM package and demo
  • GitHub Check: Run snippets and cpython tests (macos-latest)
  • GitHub Check: Check Rust code with rustfmt and clippy
  • GitHub Check: Run snippets and cpython tests (ubuntu-latest)
  • GitHub Check: Run rust tests (windows-latest)
  • GitHub Check: Run rust tests (ubuntu-latest)
  • GitHub Check: Run rust tests (macos-latest)
  • GitHub Check: Ensure compilation on various targets
🔇 Additional comments (3)
stdlib/src/binascii.rs (3)

46-161: Well-implemented enhancement to support hex separators!

The implementation correctly handles the optional separator insertion with both positive and negative bytes_per_sep values, matching Python's behavior. The error validation, optimization for simple cases, and pre-allocation of the result vector are all excellent design choices.


477-477: Good type broadening for quoted-printable encoding!

Changing from ArgAsciiBuffer to ArgBytesLike correctly allows the function to accept any bytes-like input, which aligns with Python's binascii.b2a_qp behavior that can encode any binary data.


52-53: Verify the default value for bytes_per_sep matches Python's behavior.

The implementation uses a default value of 1 for bytes_per_sep. Please ensure this matches Python's binascii.hexlify behavior.

What is the default value of bytes_per_sep parameter in Python's binascii.hexlify function when a separator is provided?
✨ 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
🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in 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.
All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@youknowone
youknowone merged commit 0728da5 into RustPython:main Jun 22, 2025
@youknowone
youknowone deleted the binascii branch June 22, 2025 23:59
@coderabbitai coderabbitai Bot mentioned this pull request Jun 25, 2025
Remove redundent to_owned() and to_string() calls #5836
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

1 participant

@youknowone
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.