Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR migrates the developer workflow to Pixi. This is pretty much aligned with what has already been done for most HoloViz packages, with some differences:
default
environment with pretty much all that is required to develop hvPlot (tests, jupyterlab, etc.), excluding building the docs (could be included). This approach was recently adopted by HoloViews. EDIT: With a bit more streamlined experience provided bypixi run install-dev
(create env, editable install, set up pre-commit, download test datasets).hatchling
to build hvPlot as I don't want to mix things too much in this PR that is already big enough.pyproject.toml
and some jobs runningpip
, I'd like to keep the option to develop hvPlot with pip (even if undocumented), I'm concerned Pixi makes the life of re-distributors too difficult (making it less likely for hvPlot to be re-distributed).