-
-
Notifications
You must be signed in to change notification settings - Fork 471
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
Pyodide Conversion: requirements.txt not able to deal with wheel-urls #6787
Comments
As pyodide does only provide one set of emscripten-wheels for every version (...) it doesn't make a lot of sense to use formal |
ALL software version info
panel@900fb095b4dfe7c3500321ba7fe84f188b08721a
on Python 3.12.2Description of expected behavior and the observed behavior
I would like to specify a custom url for a wheel in pyiodide conversion. In standard Python I can just put the url in the
requirements.txt
. As panel usespackaging.requirements.Requirement
this doesn't work, because the URL is not a valid requirement. This would not be bad if one could usepackage @ wheelurl
. However this fails, because panel passes this as a string to micropip, which doesn't understand this spec and tries to gethttp://localhost:8000/mywheel@https://localhost:8000/myhweel.whl
.According to micropip one should https://micropip.pyodide.org/en/stable/project/api.html#micropip.install only pass package names, http or emfs-urls.
Complete, minimal, self-contained example code that reproduces the issue
where
reqs.txt
looks likeresults in:
Requirements
to package specifications accepted by micropipThe text was updated successfully, but these errors were encountered: