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

!pip install nnsvs #195

Closed
AbdullahMustafa040 opened this issue Aug 30, 2023 · 6 comments
Closed

!pip install nnsvs #195

AbdullahMustafa040 opened this issue Aug 30, 2023 · 6 comments

Comments

@AbdullahMustafa040
Copy link

Collecting nnsvs
  Downloading nnsvs-0.0.3.tar.gz (109 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 109.3/109.3 kB 2.2 MB/s eta 0:00:00
  error: subprocess-exited-with-error
  
  × pip subprocess to install build dependencies did not run successfully.
  │ exit code: 1
  ╰─> See above for output.
  
  note: This error originates from a subprocess, and is likely not a problem with pip.
  Installing build dependencies ... error
error: subprocess-exited-with-error

× pip subprocess to install build dependencies did not run successfully.
│ exit code: 1
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.
@macguyversmusic
Copy link

macguyversmusic commented Aug 30, 2023

image
will you guys check this one too?
a standard call to pull the package fails as above...
installing using code in your demo creates the error below..
image
you force a quiet install but it fails and shows us no error... cant you turn off the --quiet at the repo?
manual pull and local install creates the following:
image

@AbdullahMustafa040
Copy link
Author

@r9y9

@r9y9
Copy link
Collaborator

r9y9 commented Oct 9, 2023

I was able to reproduce the issue. No idea at the moment.

@r9y9
Copy link
Collaborator

r9y9 commented Oct 9, 2023

! pip install nnsvs -vv --no-build-isolation

this should probably fix the most of installation issues.

@r9y9
Copy link
Collaborator

r9y9 commented Oct 9, 2023

BTW, I'm gonna tag a new version 0.1.0 that should resolve this issue (by #197). Hold on

@r9y9
Copy link
Collaborator

r9y9 commented Oct 9, 2023

should be solved by the latest release

@r9y9 r9y9 closed this as completed Oct 9, 2023
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

3 participants