-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update pybigtools to 0.2.2 #50026
Update pybigtools to 0.2.2 #50026
Conversation
📝 WalkthroughWalkthroughThe pull request includes modifications to two files: Possibly related PRs
Suggested reviewers
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (1)
recipes/pybigtools/build.sh (1)
Line range hint
1-37
: Consider enhancing build script robustness.The build script handles complex operations including platform-specific configurations and file movements. Consider these improvements:
- Add validation for successful wheel creation before installation
- Add error handling for the pyproject.toml move operation
- Consider adding a cleanup trap for the macOS tool symlinks
Example enhancement:
# The wheels don't seem to install as expected unless pyproject.toml is moved back into the source dir. -mv pyproject.toml pybigtools/ +if [ ! -f pyproject.toml ]; then + echo "ERROR: pyproject.toml not found" + exit 1 +fi +mv pyproject.toml pybigtools/ || { echo "Failed to move pyproject.toml"; exit 1; } # Run maturin build to produce *.whl files. maturin build -m pybigtools/Cargo.toml -b pyo3 --interpreter "${PYTHON}" --release --strip + +# Verify wheel creation +if [ ! -f pybigtools/target/wheels/*.whl ]; then + echo "ERROR: Wheel file not created" + exit 1 +fi
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (2)
recipes/pybigtools/build.sh
(1 hunks)recipes/pybigtools/meta.yaml
(3 hunks)
🔇 Additional comments (6)
recipes/pybigtools/meta.yaml (4)
14-14
: LGTM: Build number reset.
Resetting the build number to 0 for a new version is the correct practice.
35-35
: LGTM: URL formatting improvements.
The addition of quotes around URLs in the about section improves consistency and readability.
Also applies to: 40-41
46-46
: LGTM: Enhanced platform support.
Adding osx-arm64 platform support is a valuable enhancement that extends compatibility to Apple Silicon machines.
2-3
:
Version mismatch with PR objectives.
The PR description indicates an update to version 0.2.1, but the recipe shows version 0.2.2. Please verify if this is intentional or if the version needs to be adjusted to match the PR objectives.
Let's verify the latest version on PyPI:
✅ Verification successful
Version update to 0.2.2 is correct and matches PyPI
The version update to 0.2.2 in the recipe is correct as it matches the latest version available on PyPI. While the PR description mentioned updating to 0.2.1, it appears that version 0.2.2 was released during the update process, and the bot correctly updated to the latest available version. This is expected behavior for automated version updates.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Check the latest version of pybigtools on PyPI
curl -s https://pypi.org/pypi/pybigtools/json | jq -r '.info.version'
Length of output: 75
recipes/pybigtools/build.sh (2)
37-37
: Verify LICENSE file location.
The LICENSE file is being moved from pybigtools/LICENSE
to the root directory. Let's verify that this path is correct and the file exists.
#!/bin/bash
# Verify the LICENSE file exists in the expected location
if [ -f "pybigtools/LICENSE" ]; then
echo "LICENSE file exists in the expected location"
else
echo "WARNING: LICENSE file not found in pybigtools/LICENSE"
# Search for LICENSE file in other locations
fd -i license
fi
Line range hint 8-10
: Verify MacOS deployment target compatibility.
Setting MACOSX_DEPLOYMENT_TARGET=12.7
might be too restrictive as it requires macOS Monterey or newer. Consider using a lower version (e.g., 10.15) to support older macOS versions unless there's a specific requirement for 12.7.
Update
pybigtools
: 0.2.0 → 0.2.2recipes/pybigtools
(click to view/edit other files)This pull request was automatically generated (see docs).