Closed Azaya89 closed 1 month ago
Thanks! Can you tell me what steps will let me reproduce this running project? E.g. anaconda-project prepare
followed by something to use the git master version of holoviews (or maybe make a dev release?)?
Thanks! Can you tell me what steps will let me reproduce this running project? E.g.
anaconda-project prepare
followed by something to use the git master version of holoviews (or maybe make a dev release?)?
It's been updated to depend on pyviz/label/dev
. One question though, didn't we say we wanted the projects to depend on defaults
as much as possible? During the big update end of last year, I removed pyviz and conda-forge as much as possible.
Thanks! Can you tell me what steps will let me reproduce this running project? E.g.
anaconda-project prepare
followed by something to use the git master version of holoviews (or maybe make a dev release?)?
I think you can just run it the same way as before (i.e, anaconda-project run
), since I've updated the lock files to use the dev version of holoviews.
It's been updated to depend on
pyviz/label/dev
. One question though, didn't we say we wanted the projects to depend ondefaults
as much as possible? During the big update end of last year, I removed pyviz and conda-forge as much as possible.
I think this is only temporary until the new holoviews version is released. Afterwards, we can update the lock files. @Hoxbro
As @Azaya89 said, it is temporary until the next release of HoloViews is out.
Your changes were successfully integrated in the dev site, make sure to review the pages of the projects you touched before merging this PR: https://holoviz-dev.github.io/examples/. You can also download an archive of the site from the workflow summary page which comes in handy when your dev site built was overriden by another PR (we have a single dev site!).
Your changes were successfully integrated in the dev site, make sure to review the pages of the projects you touched before merging this PR: https://holoviz-dev.github.io/examples/. You can also download an archive of the site from the workflow summary page which comes in handy when your dev site built was overriden by another PR (we have a single dev site!).
As @Azaya89 said, it is temporary until the next release of HoloViews is out.
Ok noted thanks. Let's switch back to the defaults
channel when HoloViews is released with this fix.
Your changes were successfully integrated in the dev site, make sure to review the pages of the projects you touched before merging this PR: https://holoviz-dev.github.io/examples/. You can also download an archive of the site from the workflow summary page which comes in handy when your dev site built was overriden by another PR (we have a single dev site!).
Your changes were successfully integrated in the dev site, make sure to review the pages of the projects you touched before merging this PR: https://holoviz-dev.github.io/examples/. You can also download an archive of the site from the workflow summary page which comes in handy when your dev site built was overriden by another PR (we have a single dev site!).
Your changes were successfully integrated in the dev site, make sure to review the pages of the projects you touched before merging this PR: https://holoviz-dev.github.io/examples/. You can also download an archive of the site from the workflow summary page which comes in handy when your dev site built was overriden by another PR (we have a single dev site!).
Your changes were successfully integrated in the dev site, make sure to review the pages of the projects you touched before merging this PR: https://holoviz-dev.github.io/examples/. You can also download an archive of the site from the workflow summary page which comes in handy when your dev site built was overriden by another PR (we have a single dev site!).
I'm getting this warning when I run doit validate:nyc_taxi
: "WARNING: Notebook nyc_taxi/index.ipynb must not contain any code cell outputs, please clear it." but the index.ipynb
file doesn't even have any code cell output in the first place.
Does it have something to do with #377 ? @maximlt
I'm getting this warning when I run
doit validate:nyc_taxi
: "WARNING: Notebook nyc_taxi/index.ipynb must not contain any code cell outputs, please clear it." but theindex.ipynb
file doesn't even have any code cell output in the first place.Does it have something to do with #377 ? @maximlt
Good catch thanks! Should be fixed by https://github.com/holoviz-topics/examples/pull/380.
I updated your original post with the modernizing checklist.
Your changes were successfully integrated in the dev site, make sure to review the pages of the projects you touched before merging this PR: https://holoviz-dev.github.io/examples/. You can also download an archive of the site from the workflow summary page which comes in handy when your dev site built was overriden by another PR (we have a single dev site!).
I have effected most of the requested changes. Pls let me know if I missed anything while we wait for the new holoviews version to be released :)
@Azaya89 I reviewed the changes you made, they look good to me. What is left I think:
df.hvplot.<>(...).opts(bgcolor='...')
but instead df.hvplot.<>(..., bgcolor='...')
package >=X.X
) to the dependencies in the anaconda-project.yml file@Azaya89 hvPlot 0.10.0 has been released so you can now update the code to use bgcolor
directly when calling hvPlot instead of via .opts()
. When done, please ask Jim if he wants to review.
Your changes were successfully integrated in the dev site, make sure to review the pages of the projects you touched before merging this PR: https://holoviz-dev.github.io/examples/. You can also download an archive of the site from the workflow summary page which comes in handy when your dev site built was overriden by another PR (we have a single dev site!).
Your changes were successfully integrated in the dev site, make sure to review the pages of the projects you touched before merging this PR: https://holoviz-dev.github.io/examples/. You can also download an archive of the site from the workflow summary page which comes in handy when your dev site built was overriden by another PR (we have a single dev site!).
Merging, thanks @Azaya89, great job!
This PR modernizes the
nyc_taxi.ipynb
,nyc_taxi-nongeo
, anddashboard.ipynb
notebooks. After updating the dependencies however, I noticed a bug with the current holoviews version which was fixed here. This will require updating the channels when the new holoviews version is released.Modernizing an example checklist
Preliminary checks
Change ‘anaconda-project.yml’ to use the latest workable version of packages
hvplot<0.9
tohvplot
,panel>=0.12,<1.0
topanel>=0.12
) of all other dependencies. Removing the upper pins of dependencies could necessitate code revisions in the notebooks to address any errors encountered in the updated environment. Should complexities or extensive time requirements arise, document issues for team discussion on whether to re-pin specific packages or explore other solutions.hvplot
tohvplot>=0.9.2
,hvplot>=0.8
tohvplot>=0.9.2
). Usually, the new/updated lower pin of a dependency will be the version resolved afteranaconda prepare
has been run. Execute!conda list
in a notebook, oranaconda run conda list
in the terminal, to display the version of each dependency installed in the environment. Adjusting the lower pin helps ensure that the locks produced for each platform (linux-64, win-64, osx-64, osx-arm64) rely on the tested dependencies and not on some older versions.Plot API updates (discussed on a per-example basis)
datashade
withrasterize
(read this page). Essentially,rasterize
allows Bokeh to handle the colormapping instead of Datashader.Interactivity API updates (discussed on a per-example basis)
pn.interact
usage.param.watch()
usage. This is pretty low-level and verbose approach and should not be used in Examples unless required, or an Example is specifically trying to demo its usage in an advanced workflow.pn.bind()
. Read this page for explanation.view()
method and call it directly, update the class by inheriting frompn.viewable.Viewer
and replaceview()
by__panel__()
. Here is an example.Panel App updates (discussed on a per-example basis)
pn.Column
, or more complicated to incorporate widgets, etc. Make the final app.servable()
.command: dashboard
declaration in theanaconda-project.yml
file), try adding it.template = pn.template.BootstrampTemplate
, but if building up an app across multiple cells, it is probably cleaner to declare the template at the top withpn.extension(template='bootstrap')
. See how to guide on setting a template.General code quality updates
warnings.simplefilter(‘ignore’)
somewhere at the start of the notebook, remove this line. Try to update the code to remove the warnings, if any. If updating the code to remove the warnings is taking significant amount of time and effort, bring it up for discussion and we may decide to disable warnings again.Text content
Visual appearance - Example
Visual appearance - Gallery
Ml Annotators
toML Annotators
), if not, add/update theexamples_config.title
field inanaconda-project.yml
description
field inanaconda-project.yml
Workflow (after you have made the changes above)
doit validate:<projectname>
doit test:<projectname>
doit doc_one –name <projectname>
. It’s better if the project notebook(s) is saved with its outputs (but be sure to clear outputs before committing to the examples repo!) when building the docs. Then open this file in your browser./builtdocs/index.html
and check how the site looks.