Jake Vanderplas

Altair 4.1 changed it's `save` to use `altair_saver` under the hood, so this bug is likely related to failing to plumb that value through correctly.

This is unavoidable, unfortunately. These docs come directly from the vega-lite schema documentation. Altair currently builds from Vega-Lite version 4, but the vega-lite website is built with Vega-Lite version 5,...

This would be good to document. In short, `alt.value()` specifies a constant range value, while `alt.datum` specifies a domain value. So `x=alt.value(100)` would place a mark 100 pixels from the...

I've been wanting `alt.datum` forever - it was such a relief to finally have that functionality available in the last release!

Another good example: `color=alt.datum('label')` creates a mark with whatever color is associated with the value `"label"` in the color scale, while `color=alt.value('red')` creates a red mark regardless of the color...

Great suggestion! All datasets accessed by this package come from the [vega/vega-datsets](https://github.com/vega/vega-datasets) repository. Any new datasets should be proposed there.

I don't think the full URL is actually required. For example, I ran this in a local JupyterLab instance and it produced a correctly rendered chart: ```python import altair as...

Just a note, since I was credited with this: I'm not certain this is the correct fix. What I am certain of is that certain ufuncs in the NumPy documentation...

Thanks for the report - it looks like we forgot to call `_check_user_dtype_supported`.

Thanks for the request. Related feature requests are at #9956 and #11002.