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
In general, I don't think it's a good idea for a pure Python library like Altair to have a hard dependency on a native library if it can be avoided. This would break the use of Altair in contexts where vl-convert-python isn't pre-compiled. One notable example would be pyodide/pyscript. But also various arm architectures that are pre-built yet.
We could add vl-convert-python to an extra_require group and then update the docs to install using that group. For example, we could add vl-convert-python, altair-viewer, and vega-datasets to an extra_require group named full and then instruct people in the docs to install altair with
Lets open this issue. Title says it all. What are the cons and pros?
Pros:
Cons:
The text was updated successfully, but these errors were encountered: