Update kb-python to 0.29.1

[BiocondaBot]

Update kb-python: 0.28.2 → 0.29.1

Info	Link or Description
Recipe	recipes/kb-python (click to view/edit other files)
Summary	A wrapper for the kallisto
Home	https://github.com/pachterlab/kb_python
Releases	https://github.com/pachterlab/kb_python/tags
Recipe Maintainer(s)	@Maarten-vd-Sande
Author	@pachterlab

---

This pull request was automatically generated (see docs).

[coderabbitai]

📝 Walkthrough

📝 Walkthrough

Walkthrough

The pull request introduces updates to the meta.yaml file for the kb-python package. The package version is incremented from 0.28.2 to 0.29.1, and the source URL is modified to point to the new version's tarball. The SHA256 checksum is updated to ensure the integrity of the new version. Additionally, the build number is reset from 2 to 0, and the build script is altered to include the --no-cache-dir option in the pip installation command. The requirements section has undergone significant modifications: the Python version constraint has been updated from >=3.7, <3.9 to >=3.8, and several dependencies have updated version constraints, including anndata, ngs-tools, and pandas. A new dependency, biopython, has been added with a constraint of >=1.8. The summary in the about section has been slightly modified, and a new identifiers section has been added, including a DOI reference. Overall, the changes primarily involve version updates, adjustments to dependency constraints, and minor modifications to the metadata.

Possibly related PRs

• Update python to >=3.8 in k8 recipe #51054: This PR updates the k8/meta.yaml file to change the Python version requirement from an exact version (==3.8) to a minimum version (>=3.8), which is directly related to the changes in the main PR that also updated the Python version constraint in kb-python/meta.yaml from >=3.7, <3.9 to >=3.8.
• Update meta.yaml for spec2vec #49857: This PR updates the spec2vec/meta.yaml file to change the build script to include the --no-cache-dir option, similar to the changes made in the main PR where this option was added to the pip install command in kb-python/meta.yaml.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between a07b65d and a4f019f.

📒 Files selected for processing (1)

• recipes/kb-python/meta.yaml (2 hunks)

🧰 Additional context used

🔇 Additional comments (7)

recipes/kb-python/meta.yaml (7)

2-2: Version update looks good.

The package version has been correctly updated to 0.29.1, which aligns with the PR objectives.

---

13-15: Build section changes are appropriate.

The build number has been correctly reset to 0 for the new version. The addition of --no-cache-dir to the pip install command is a good practice to ensure a clean build.

---

23-25: Host requirements update looks good, but needs verification.

The minimum Python version has been increased to 3.8. This change is likely intentional, but it's important to ensure it doesn't break compatibility with existing systems.

Please confirm that this change is intentional and aligns with the package's compatibility requirements. You may want to check the package's release notes or documentation for any mentions of increased Python version requirements.

---

56-56: Minor improvement to summary formatting.

The addition of a period at the end of the summary improves its formatting.

---

63-64: Addition of DOI identifier is valuable.

The inclusion of a DOI in the identifiers section is beneficial for package identification and citation.

Please verify the correctness of the DOI by checking it against the package's documentation or publication. You can use the following URL to verify:
https://doi.org/10.1101/2023.11.21.568164

---

9-10: Source URL and checksum update look correct.

The source URL has been updated to reflect the new version, and a new SHA256 checksum has been provided.

Please run the following script to verify the checksum:

#!/bin/bash
# Description: Verify the SHA256 checksum of the source tarball

# Download the tarball
curl -L https://github.com/pachterlab/kb_python/archive/v0.29.1.tar.gz -o kb_python-0.29.1.tar.gz

# Calculate and compare the checksum
echo "f94e20d592dfd6e7d50b470c0d83732bfb34c6f9c822f22714dac0bb98f87aa3 kb_python-0.29.1.tar.gz" | sha256sum --check

# Clean up
rm kb_python-0.29.1.tar.gz

---

27-43: Run requirements updates look appropriate, but need verification.

The dependency updates and the addition of biopython (>=1.8) likely reflect new compatibility requirements or features in the updated package version.

Please run the following script to verify these changes against the package's setup.py or pyproject.toml:

Ensure that the changes in the recipe align with the package's actual requirements.

---

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?

❤️ 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 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.