Open therc01 opened 2 months ago
getting this when doing pip3 install
Hello, Sorry, I've only tested the code on Ubuntu and Windows 11 and I don't have a computer with macOS at my disposal... The problem seems to be more related to the ShazamIO package, but I saw that you had already added a issue about it. Don't hesitate if you have an answer or if you've found a solution, to write it here, so I can maybe fix the problem. Good luck in any case!
Sure
@therc01 I'm using the library just fine on macOS M1 chip, but I use poetry
and not pip to manage my packages. You might try that.
getting this
Collecting shazamio-core<2.0.0,>=1.0.7 (from shazamio) Using cached shazamio_core-1.0.7.tar.gz (2.2 kB) Installing build dependencies ... done Getting requirements to build wheel ... done Preparing metadata (pyproject.toml) ... error error: subprocess-exited-with-error
× Preparing metadata (pyproject.toml) did not run successfully. │ exit code: 1 ╰─> [5 lines of output] 💥 maturin failed Caused by: Can't find /private/var/folders/qw/h4rml07d7tgg8rk7n74zz7bm0000gn/T/pip-install-v20bfs9n/shazamio-core_99820c2f6dbb4ca4a69a735798cb5690/Cargo.toml (in /private/var/folders/qw/h4rml07d7tgg8rk7n74zz7bm0000gn/T/pip-install-v20bfs9n/shazamio-core_99820c2f6dbb4ca4a69a735798cb5690) Error running maturin: Command '['maturin', 'pep517', 'write-dist-info', '--metadata-directory', '/private/var/folders/qw/h4rml07d7tgg8rk7n74zz7bm0000gn/T/pip-modern-metadata-nibupmsw', '--interpreter', '/Library/Frameworks/Python.framework/Versions/3.10/bin/python3']' returned non-zero exit status 1. Checking for Rust toolchain.... Running
maturin pep517 write-dist-info --metadata-directory /private/var/folders/qw/h4rml07d7tgg8rk7n74zz7bm0000gn/T/pip-modern-metadata-nibupmsw --interpreter /Library/Frameworks/Python.framework/Versions/3.10/bin/python3
[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.