We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
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.
pio.kaleido.scope.plotlyjs
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.
The text was updated successfully, but these errors were encountered:
plotlyjs
kaleido.*
PageGenerator
emilykl
Successfully merging a pull request may close this issue.
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:
But with Plotly.py v6.1.2 and Kaleido v1 it gives the following error:
IMO there's no reason to stop supporting this option and it should be relatively straightforward to pass through into Kaleido v1.
The text was updated successfully, but these errors were encountered: