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
pivy-importer: how to include a package from a URL/wheel file #46
Comments
Right now we point specifically at pypi to get the artifact. You could either update make it where it will accept a URL or you could generate the Ivy file manually. I think the importer can handle Wheels, so it might make more since to just have it able to accept a URL as input. We accept PR's :-) |
Can you give an example/hint on how to tell the importer to handle wheels? I can work on getting it from the URL. If everything works, I can send a PR. |
So it looks like you'll have to implement something to parse Wheel files metadata, somewhat like SourceDistPackage does. To so this you'll probably want to look at Here is the spec for wheels: https://www.python.org/dev/peps/pep-0427/ Does this help get you started? |
thanks. This seems more involved than I have bandwidth for :( For doing it manually: how do I get the files that are supposed to be in the |
You should be able to just use the wheel format without unzipping it. You'll have to set the artifact name to be right, along with the extensions but it should work. I haven't tested it in a long time, we don't use wheels internally so I can't guarantee it will work. We're looking at making a better story around wheels though. |
It gives an exception it doesn't understand the
My
|
:-( thats sad. I guess it's not supported... @sholsapp any ideas here? |
E.g. the library
tensorflow
is not in pypi. Instead the instructions to install the library areHow do I include this package in the
ivy-repo
generated bypivy-importer
?The text was updated successfully, but these errors were encountered: