Skip to content

Comments

Clarify supported Python versions and document CUDA dependency issues#281

Open
mahek2016 wants to merge 1 commit intoAOSSIE-Org:mainfrom
mahek2016:docs/improve-installation-guide
Open

Clarify supported Python versions and document CUDA dependency issues#281
mahek2016 wants to merge 1 commit intoAOSSIE-Org:mainfrom
mahek2016:docs/improve-installation-guide

Conversation

@mahek2016
Copy link

@mahek2016 mahek2016 commented Feb 16, 2026

Closes #272

📝 Description

This pull request improves the installation and onboarding documentation for new contributors.

While setting up the project locally, I encountered issues related to unsupported Python versions and CUDA-related dependencies. These were not clearly documented, which may cause confusion for first-time contributors.

This update clarifies:

  • Supported Python versions (>=3.10 and <3.13)
  • Python 3.13 incompatibility issues
  • CUDA/NVIDIA dependency installation failures
  • Recommended use of Docker for consistent setup

These changes reduce onboarding friction and improve the overall contributor experience.

🔧 Changes Made

  • Updated Python version requirement in prerequisites section
  • Added warning about Python 3.13 incompatibility
  • Added CUDA/GPU dependency notice section
  • Documented common installation error:
    ERROR: No matching distribution found for nvidia-cufile-cu12
  • Suggested Docker as recommended setup for consistency

📷 Screenshots or Visual Changes (if applicable)

Not applicable – documentation update only.

🤝 Collaboration

Collaborated with: N/A

✅ Checklist

  • I have read the contributing guidelines.
  • I have added tests that prove my fix is effective or that my feature works.
  • I have added necessary documentation (if applicable).
  • Any dependent changes have been merged and published in downstream modules.

Summary by CodeRabbit

  • Documentation
    • Updated Python version requirements (3.10–3.12, with 3.11 recommended); noted Python 3.13 incompatibility
    • Added GPU/CUDA dependency information for NVIDIA systems, including installation guidance and troubleshooting workarounds

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 16, 2026

📝 Walkthrough

Walkthrough

Documentation update to the installation guide refining Python version requirements (≥ 3.10, < 3.13, with 3.11 recommended) and introducing a new GPU/CUDA dependency notice with troubleshooting guidance for NVIDIA-related package installation failures.

Changes

Cohort / File(s) Summary
Installation Guide Updates
docs/INSTALL_GUIDE.md
Updated Python version constraints and added CUDA dependency documentation. Changed recommended Python from 3.10 to 3.11 for Poetry environment; added explicit 3.13 compatibility warning; introduced GPU/CUDA Dependency Notice section detailing NVIDIA packages, common installation failures, and workarounds.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 With whiskers twitching at version bounds,
I hopped through docs with curious bounds,
Python three-eleven hops just right,
While CUDA warnings shine so bright!
Now newcomers find their way with cheer,
The installation path is crystal clear! 🚀

🚥 Pre-merge checks | ✅ 5 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Linked Issues check ⚠️ Warning The PR partially addresses issue #272 objectives by documenting CUDA dependency issues and clarifying Python versions, but does not document environment variables or add a comprehensive Common Errors section as requested. Complete the remaining requirements from #272: document environment variables in .env.example file and expand the Common Errors section to cover additional setup issues beyond CUDA.
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately and concisely describes the main changes to the INSTALL_GUIDE.md documentation, directly addressing Python version clarification and CUDA dependency documentation.
Out of Scope Changes check ✅ Passed Changes are focused on installation documentation and are aligned with the PR objectives; however, the scope is narrower than the linked issue requirements.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection ✅ Passed ✅ No merge conflicts detected when merging into main

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.


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

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Fix all issues with AI agents
In `@docs/INSTALL_GUIDE.md`:
- Around line 55-59: Add a language tag to the fenced code block that contains
the error snippet "ERROR: No matching distribution found for nvidia-cufile-cu12"
by changing the opening triple backticks to include a language (e.g., use
```text or ```sh) so the block is lint-compliant (MD040) and displays as plain
text; locate the fenced block around that error message and update its opening
fence accordingly.

Comment on lines +55 to +59
If you encounter errors such as:

```
ERROR: No matching distribution found for nvidia-cufile-cu12
```
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Add a language to the fenced error snippet.

The fenced block for the error message lacks a language tag, triggering MD040. Suggest using text (or sh) for clarity and lint compliance.

🔧 Suggested fix
-```
-ERROR: No matching distribution found for nvidia-cufile-cu12
-```
+```text
+ERROR: No matching distribution found for nvidia-cufile-cu12
+```
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
If you encounter errors such as:
```
ERROR: No matching distribution found for nvidia-cufile-cu12
```
If you encounter errors such as:
🧰 Tools
🪛 markdownlint-cli2 (0.20.0)

[warning] 57-57: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

🤖 Prompt for AI Agents
In `@docs/INSTALL_GUIDE.md` around lines 55 - 59, Add a language tag to the fenced
code block that contains the error snippet "ERROR: No matching distribution
found for nvidia-cufile-cu12" by changing the opening triple backticks to
include a language (e.g., use ```text or ```sh) so the block is lint-compliant
(MD040) and displays as plain text; locate the fenced block around that error
message and update its opening fence accordingly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

DOCS UPDATE:Improve installation and environment variable documentation for new contributors

1 participant