include the skrub wheel in the built documentation
Opened this issue · 2 comments
jeromedockes commented
at the moment for jupyterlite we hardcode the link to a particular skrub version on pypi:
Line 386 in b5962f7
however that version may not be the right one, and the right one may not be on pypi yet (eg when running the examples for the dev/ documentation, or when we make a release there is a chicken-egg problem:we would like to write the correct pypi link before releasing, but it doesn't exist before the release)
it would be better to build the wheel as a part of building the documentation and include it as a static asset. then in jupyterlite we would pip install the wheel that is in the same directory of the current site rather than a hardcoded one from pypi
GaelVaroquaux commented
It would help indeed, and having a nightly as part of the dev docs would be amazing!
jeromedockes commented