Walkthrough

Removed the top-level jit workspace member and updated workspace dependency paths; adjusted the JIT crate's dev-dependency to use workspace = true instead of an explicit local path/version.

Changes

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Focus points:
  • Confirm no remaining references to the removed top-level jit member in CI/build scripts.
  • Verify workspace dependency resolution produces a single expected version for rustpython-jit and rustpython-derive.
  • Ensure local development workflows (e.g., cargo commands, IDE workspace) still work with the new paths.

Suggested reviewers

• youknowone

Poem

🐇 I nudged a crate from root to stack,
Paths adjusted — no looking back.
Derive now reads from workspace tree,
Quiet changes, tidy and free. 🥕

Pre-merge checks and finishing touches

Learnt from: reactive-firewall
Repo: RustPython/RustPython PR: 6176
File: .github/workflows/Check_Tests.yml:133-141
Timestamp: 2025-09-28T22:22:55.921Z
Learning: In the RustPython project's CI-5974-Test-RustPython-Integration action, the override-rustpython-path input is marked as required but has runtime fallback logic that defaults to RUSTPYTHONPATH environment variable or "Lib" if neither is provided, making explicit specification unnecessary in most cases.

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.

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