plotly 6.0.1

[skupr-anaconda]

Destination channel: main

Links

• Jira
• Upstream repo
• release-diff: plotly/plotly.py@v5.24.1...v6.0.1
• changelog: https://github.com/plotly/plotly.py/blob/main/CHANGELOG.md
• requirements-tagged:
  • https://github.com/plotly/plotly.py/blob/v6.0.1/pyproject.toml

Explanation of changes:

• Reset build number from 1 to 0
• Remove tenacity from run
• Remove several import tests for modules that have been deprecated or removed:

_plotly_utils
_plotly_utils.colors
_plotly_future_
plotly.graph_objs.heatmapgl
plotly.graph_objs.pointcloud
plotly.validators.heatmapgl
plotly.validators.pointcloud

• Completely remove abs.yaml file

Notes:

• I've tested the package with donwstreams:

Downstream build order (groups:() feedstocks:('plotly-feedstock',) packages:() allow_list:() block_list:() drop_noarch:False sections:('build', 'host', 'run')):

000 dash-feedstock                 ['dash']
001 anaconda-feedstock             ['_anaconda_depends', '_anaconda_core', '__anaconda_core_depends']
001 chart-studio-feedstock         ['chart-studio']
001 plotly-resampler-feedstock     ['plotly-resampler']
002 anaconda_custom-feedstock      ['anaconda']
002 autovizwidget-feedstock        ['autovizwidget']
002 bertopic-feedstock             ['bertopic']
002 catboost-feedstock             ['catboost']
002 dash-bio-feedstock             ['dash-bio']
002 glue-core-feedstock            ['glue-core']
002 interpret-feedstock            ['interpret']
002 python-cufflinks-feedstock     ['python-cufflinks']
002 sdmetrics-feedstock            ['sdmetrics']
002 statsforecast-feedstock        ['statsforecast']
002 streamlit-plotly-events-feedstock ['streamlit-plotly-events']

No issues found.

[skupr-anaconda]

An error on win-64:

usage: py_compile.py [-h] [-q] filenames [filenames ...]
py_compile.py: error: the following arguments are required: filenames

[Andrii-Osipov]

LGTM - but missing imports

[bwingconda]

Is it worth trying to run their unit tests or do they require our CI to have a head? As Andrii pointed out, there are also a fair number of new import paths that could be checked.

[skupr-anaconda]

Is it worth trying to run their unit tests or do they require our CI to have a head? As Andrii pointed out, there are also a fair number of new import paths that could be checked.

There are unusually long builds on Windows, see also plotly/plotly.py#1208. I'm afraid that enabling tests for Windows will take more than 4-6 hours. But I can try on Unix platforms

[skupr-anaconda]

Is it worth trying to run their unit tests or do they require our CI to have a head? As Andrii pointed out, there are also a fair number of new import paths that could be checked.

There are unusually long builds on Windows, see also plotly/plotly.py#1208. I'm afraid that enabling tests for Windows will take more than 4-6 hours. But I can try on Unix platforms

The source code on PyPI doesn't contain tests, so I'll skip it for now.