-
Notifications
You must be signed in to change notification settings - Fork 37
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
Switch to GR or Plots for plotting and guide people to use 1.9 #554
Comments
@Roger-luo We can try to make these a weak dependence but It doesn't look like Julia 1.9 is being widely yet so perhaps splitting the visualization tools into its own sub-package would be best? |
There are a few things that can be done here:
after the above steps, we can start moving things into weakdeps. |
Pending more python functionality, perhaps we can try more towards (1)? This way the user can choose their own plotting backends and where necessary (eg visualizing waveforms) a julia plot can do. Is 1.9 necessary for that? |
nope, the only difference is on 1.9 the experience will be much better because the latency of the first plot will be unnoticeable. So compatibility is guaranteed to all 1.x versions, tho 1.9 is recommended. But this was the main reason why we were not using Plots/GR because there was no option for good UX back then. |
Confirm that Bloqade does not need Python as a dependency. I think that when Bloqade is installed, it also adds an entire conda environment. This can sometimes run into environment issues.
This should perhaps extend to all of our examples too. That is a little harder, of course, because Python plots are pretty. However, it does remove a barrier to running examples!
The text was updated successfully, but these errors were encountered: