You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
.../.venv/lib/python3.10/site-packages/kaleido/scopes/base.py:188: DeprecationWarning:
setDaemon() is deprecated, set the daemon attribute instead
This appears when warnings are enabled, such as python -W default ... or running tests under pytest.
All-in-one reproducer:
# do it all in a temporary directory/venvcd$(mktemp -d)
python3.10 -m venv .venv
# install all dependencies
.venv/bin/python -m pip install kaleido==0.2.1 plotly==5.21.0 tenacity==8.2.3 packaging==24.0
# BUG: run to_image, with warnings enabled:
.venv/bin/python -W default -c 'from plotly.graph_objs import Figure; Figure().to_image()'# DeprecationWarning: setDaemon() is deprecated, set the daemon attribute instead
Based on #171, this can probably be resolved by doing a new release of Kaleido to PyPI & conda, since #146 appears to fix it in the unreleased code on the master branch.
Alternatively, if Kaleido is unmaintained (and thus may stop working with future Python versions), maybe Plotly.py needs to support another engine?
Thanks for Plotly!
The text was updated successfully, but these errors were encountered:
Thanks for your interest in Kaleido. We are currently working on an overhaul that might address your issue - we hope to have news in a few weeks and will post an update then. Thanks - @gvwilson
Hi everyone, I'll add this to my watch. I think the new major release is coming around tomorrow. We're doing our best to squash all bugs and improve debugging before that release.
The new release of kaleido is a bit different because for many reasons, but majorly, it no longer bundles chrome.
If one executes
to_image
with Python 3.10 or greater, there is deprecation warning aboutsetDaemon
:This appears when warnings are enabled, such as
python -W default ...
or running tests under pytest.All-in-one reproducer:
Based on #171, this can probably be resolved by doing a new release of Kaleido to PyPI & conda, since #146 appears to fix it in the unreleased code on the
master
branch.Alternatively, if Kaleido is unmaintained (and thus may stop working with future Python versions), maybe Plotly.py needs to support another engine?
Thanks for Plotly!
The text was updated successfully, but these errors were encountered: