Skip to content

Manually setting Plotly.js path is not possible with Kaleido v1 #5206

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

Open
emilykl opened this issue May 27, 2025 · 0 comments · May be fixed by #5207
Open

Manually setting Plotly.js path is not possible with Kaleido v1 #5206

emilykl opened this issue May 27, 2025 · 0 comments · May be fixed by #5207
Assignees
Labels
bug something broken P1 needed for current cycle regression this used to work

Comments

@emilykl
Copy link
Contributor

emilykl commented May 27, 2025

Previously, for image export, it was possible to pass a local path and/or custom URL for Plotly.js by setting pio.kaleido.scope.plotlyjs. This is not documented but it's nonetheless used by our own image test pipeline in Plotly.js.

The following works in Plotly.py v6.0.1, as well as v6.1.2 with Kaleido v0:

import plotly.io as pio

pio.kaleido.scope.plotlyjs = "path/to/local/plotly.js"

But with Plotly.py v6.1.2 and Kaleido v1 it gives the following error:

AttributeError: 
Attribute plotly.io.defaults.plotlyjs is not valid.

IMO there's no reason to stop supporting this option and it should be relatively straightforward to pass through into Kaleido v1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug something broken P1 needed for current cycle regression this used to work
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants