fix: relax scipy version constraint for Windows Python 3.9 compatibility

[Satyanarayana001]

Fixes #382

Problem

scipy==1.14.0 is not available for Python 3.9 on Windows,
blocking backend setup for contributors.

Fix

Relaxed scipy version constraint from ==1.14.0 to >=1.11.0
allowing pip to install the best compatible version automatically.

Summary by CodeRabbit

• Chores
  • Broadened SciPy dependency range to allow installation of any compatible 1.11.x–1.x release (up to, but not including, 2.0.0), improving compatibility across environments and easing upgrades.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 9d07626e-8bc7-4175-bfca-97634ee11d18

📥 Commits

Reviewing files that changed from the base of the PR and between 39f398e and 8280c85.

📒 Files selected for processing (1)

• requirements.txt

✅ Files skipped from review due to trivial changes (1)

• requirements.txt

---

📝 Walkthrough

Walkthrough

The scipy entry in requirements.txt was changed from a fixed pin (scipy==1.14.1) to a ranged constraint (scipy>=1.11.0,<2.0.0), allowing installation of any compatible SciPy release within that interval.

Changes

Cohort / File(s)	Summary
Dependency Update requirements.txt	Relaxed scipy constraint from pinned scipy==1.14.1 to range scipy>=1.11.0,<2.0.0 (single-line change).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 I hopped through pins and loosened a thread,
Now scipy can dance where it once was led.
Installers smile, wheels softly turn,
A gentler rule helps setups run! 🥕✨

🚥 Pre-merge checks | ✅ 5

✅ 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 describes the main change: relaxing the scipy version constraint to address Windows Python 3.9 compatibility issues.
Linked Issues check	✅ Passed	The PR directly addresses issue #382 by relaxing the scipy version constraint from ==1.14.0 to >=1.11.0,<2.0.0, enabling automatic installation of compatible versions on Windows Python 3.9.
Out of Scope Changes check	✅ Passed	The PR only modifies the scipy dependency specification in requirements.txt, which is directly scoped to resolve the linked issue with no extraneous changes.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

📝 Coding Plan

• Generate coding plan for human review comments

---

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

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

[coderabbitai]

🧹 Nitpick comments (1)

requirements.txt (1)

8-8: Consider adding an upper bound to scipy for improved stability.

The change from a pinned version to scipy>=1.11.0 successfully resolves the Windows Python 3.9 installation issue. SciPy 1.11.0 wheels are available for Python 3.9 Windows, and it satisfies scikit-learn 1.5.2's dependency requirement (scipy>=1.6.0).

However, without an upper bound, future scipy releases could introduce unexpected behavior. Since most other dependencies in requirements.txt are pinned to specific versions, consider constraining scipy with scipy>=1.11.0,<2.0.0 to balance flexibility with reproducibility.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@requirements.txt` at line 8, Update the scipy requirement in requirements.txt
from a loose lower-bound to a constrained range to prevent future-breaking
upgrades; change the entry for "scipy" (the existing scipy>=1.11.0 line) to
include an upper bound such as "scipy>=1.11.0,<2.0.0" so you retain the fix for
Python 3.9 while preserving reproducibility.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@requirements.txt`:
- Line 8: Update the scipy requirement in requirements.txt from a loose
lower-bound to a constrained range to prevent future-breaking upgrades; change
the entry for "scipy" (the existing scipy>=1.11.0 line) to include an upper
bound such as "scipy>=1.11.0,<2.0.0" so you retain the fix for Python 3.9 while
preserving reproducibility.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: df9e4f84-88a9-4a67-9b2c-b82954142942

📥 Commits

Reviewing files that changed from the base of the PR and between 2038116 and 39f398e.

📒 Files selected for processing (1)

• requirements.txt

[Aditya30ag]

@Satyanarayana001
the issue has already been closed so there is no point of opening a PR !!!