Skip to content
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

new dependency to Rust / CARGO #2282

Open
cforce opened this issue Jan 17, 2025 · 1 comment
Open

new dependency to Rust / CARGO #2282

cforce opened this issue Jan 17, 2025 · 1 comment
Assignees

Comments

@cforce
Copy link
Contributor

cforce commented Jan 17, 2025

I have migrated to python 3.13.1 and hyve setup my ven from scratch and sudenly RUST dependencies are required which was not before. Is this intended to be?

Installing dependencies from requirements.txt into virtual environment .venv (in quiet mode)...

  error: subprocess-exited-with-error
  
  × Preparing metadata (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [6 lines of output]
      
      Cargo, the Rust package manager, is not installed or is not on PATH.
      This package requires Rust and Cargo to compile extensions. Install it through
      the system's package manager or via https://rustup.rs/
      
      Checking for Rust toolchain....
      [end of output]
  
  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.
Failed to restore backend python packages
@pamelafox
Copy link
Collaborator

This is due to us having to support both Python 3.9 and Python 3.13, but there not being a numpy version that has having support for both. I have an idea for a way to change our requirements file to pull in the right numpy depending on your system's Python version, which should mean no rust is needed. I'll try it out next week. Thanks for filing, this was bothering me too.
For now, you can upgrade the numpy version in requirements.txt to the latest version in your fork.

@pamelafox pamelafox self-assigned this Jan 18, 2025
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

No branches or pull requests

2 participants