Python: improve devmode logging and pre-release SDK usage

[jhaynie]

Summary by CodeRabbit

• Bug Fixes
  • Improved compatibility with Python package versions containing "+" by ensuring they are correctly interpreted and parsed.
  • Enhanced log display by supporting additional Python log prefixes for info and warning messages.

[coderabbitai]

Walkthrough

The updates introduce enhanced handling of Python package version strings in the internal bundler logic, specifically ensuring semver compliance for local builds. Additionally, the terminal UI logger now recognizes and correctly categorizes two new Python-style log prefixes for informational and warning messages.

Changes

File(s)	Change Summary
internal/bundler/upgrade.go	Modified logic in getSDKVersionPython to always process "agentuity" package versions, reformatting local build versions with "+" into semver-compliant strings before parsing.
internal/dev/tui_logger.go	Added support for Python log prefixes "[INFO ]" and "[WARNI]" in the log prefix-to-level mapping.

Poem

In the warren where code does run,
Python logs now shine like the sun.
Semver strings are neat and bright,
Even "+" signs parsed just right.
Rabbits cheer with every fix—
Hopping forward, code that clicks!
🐇✨

---

📜 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 47a866d and ed7375c.

📒 Files selected for processing (2)

• internal/bundler/upgrade.go (1 hunks)
• internal/dev/tui_logger.go (1 hunks)

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

• GitHub Check: Analyze (go)

🔇 Additional comments (2)

internal/dev/tui_logger.go (1)

114-115: Improved Python log format support

The addition of these Python-specific log prefixes enhances the logger's compatibility with Python logging output. This is a well-implemented change that maintains the existing pattern while extending functionality.

internal/bundler/upgrade.go (1)

180-187: Good handling of non-standard Python version formats

This change properly handles Python local build versions that include a "+" character, which aren't semver-compliant by default. The implementation converts these versions to a semver-compliant format by reformatting them with a "-prerelease" suffix.

The comments explain the purpose clearly, and the implementation is straightforward and effective. This will prevent parsing errors when working with local/development builds of the Python SDK.

✨ Finishing Touches

• 📝 Generate Docstrings

---

🪧 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.