-
Notifications
You must be signed in to change notification settings - Fork 55
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
Unpinning Plotly #85
Comments
Good question! An API change in plotly 4.1 broke one of our tests, but I'm not sure it actually broke the underlying functionality. So for the time being, I think you should be able to just use plotly 4.1 without breaking pygsti. Please let us know if that breaks anything. @enielse Thoughts? Here's the build that broke on |
I haven't looked into this on the pyGSTi side, but I'm hitting this with Plotly 4.1.0:
|
Just double checked on this, and the above is due to my mistakenly being on an older tag of pyGSTi. Indeed things do seem to work on the latest tag. Sorry for the false alarm. |
Actually I think this is still an issue, even though I'm no longer immediately blocked. Ideally we would still unpin the Plotly version, so maybe my closing it was premature. |
Hi there, I'm using pyGSTi in a project where I'd also like to use Plotly 4.1. I noticed #55 where there's a remark about unpinning the Plotly version in the future, and it looks like there was an attempt to do that before it was pinned again to 3.10. Just curious what the path to unpinning this looks like?
The text was updated successfully, but these errors were encountered: