Jake Vanderplas

Thanks! I'll look for your new commit.

Thanks – this implementation is very much a work in progress, but one on which I'm not progressing much lately. I'm aware that it doesn't follow the paper exactly at...

Partly addressed in 50589569180fe9f3c2a5e59768f285c297d6c399 Leaving this open in case I missed any of the essential API.

I believe vegascope does not yet support the Altair v4 renderer entrypoint: https://github.com/scikit-hep/vegascope/blob/08cd5a3983cea8a057c7d17d548d463ba1ca4900/setup.py#L56

OK – yes, I developed ``altair_viewer`` as an alternative to the functionality here, partly because I know the maintenance burden of being a "recommended" solution for a project like Altair...

> Is that true of altair_viewer: does it support the same use cases (and possibly more)? Yes - although it lacks some of the polish of vegascope (e.g. dynamic resizing,...

The easiest thing would just be to error if `copy=False` and `device` is specified.

Yash - the issue is that the semantics of `copy=False` are "error if a copy is required", so `device_put` handling that transparently doesn't help because we need to know what's...

That's what I suggested above: the most conservative thing would be to error if `copy` and `device` are used together. But the more "correct" thing would be to somehow introspect...

Thanks for the followup!