Support Vega-Lite v1 and v2?

[jakevdp]

A thought I had, and I was wondering if people would be in favor: we could technically support multiple versions of Vega-Lite within Altair. I would imagine structuring it something like this:

• If you do import altair as alt, you would get the latest version
• If you do import altair.v1 as alt, you get the syntax of altair 1.0
• If you do import altair.v2 as alt, you get the syntax of altair 2.0

We could decide how fine-grained to be in our versions (for example, do you distinguish between v1.1 and v1.2?) I think this would be quite useful during updates like that for 2.0, where there are going to be some significant backward incompatibilites.

Thoughts on that?

[ellisonbg]

That is similar to how we version things in nbformat. It is a pretty nice approach in many respects. There are also questions related to semantic versioning. Would `v1` pull give the latest release or the first one. But overall, I like this type of thing. Is your thought to keep the vega python stuff in a separate package?

…

On Tue, Aug 15, 2017 at 11:59 AM, Jake Vanderplas ***@***.***> wrote: A thought I had, and I was wondering if people would be in favor: we could technically support multiple versions of Vega-Lite within Altair. I would imagine structuring it something like this: - If you do import altair as alt, you would get the latest version - If you do import altair.v1 as alt, you get the syntax of altair 1.0 - If you do import altair.v2 as alt, you get the syntax of altair 2.0 We could decide how fine-grained to be in our versions (for example, do you distinguish between v1.1 and v1.2?) I think this would be quite useful during updates like that for 2.0, where there are going to be some significant backward incompatibilites. Thoughts on that? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#375>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABr0GpA7YNMKsltevyfWla4Oj8DyOpdks5sYeqggaJpZM4O3-ac> .

-- Brian E. Granger Associate Professor of Physics and Data Science Cal Poly State University, San Luis Obispo @ellisonbg on Twitter and GitHub [email protected] and [email protected]

[kanitw]

FYI, we store JSON schema of Vega and Vega-Lite using similar pattern: v3 for latest v3, v3.1 for latest v3.1 and v3.1.1 for specific version. (See https://github.com/vega/schema/tree/master/vega-lite.)

[kanitw]

Would v1 pull give the latest release or the first one.

I would vote for latest, similar to how we handle the schema. :)

[jakevdp]

Cool – I'm working on a quick refactor of the schema generation tools that would support this.

[ellisonbg]

I went ahead and merged #377 - we can follow up and iterate further if needed.