Altair: `vega` version 3

Created on 11 Sep 2018  路  12Comments  路  Source: altair-viz/altair

I鈥檇 like to make a new vega package release because I want to build things with Vega-Lite 3. Would it make sense to update the docs to ask people to install vega>=1.0.0? How should we go about this issue in the future? I don't want to make a new package just because of the version change.

Most helpful comment

Done

screen shot 2018-10-25 at 10 27 17

All 12 comments

Maybe we could wrap more than one version of vega/vega-lite into the ipyvega package, so we can provide entrypoints for both versions at once. It would double the size of the install, but I think the installation is not too large at the moment.

I'm worried about how this will work in the future when we have more than two versions. We would still need a policy for deprecating old versions so I wonder what would be the cleanest way forward. Or do you think this is temporal and thus warrants an exception?

Yeah, that's an issue... My first thought is that we could plan to make certain the vega package supports whatever vega-lite versions are available in Altair (currently v1 and v2, changing to v2 and v3 in the next release) then it would mostly be transparent to users.

My hope was that we could ask people to install the right vega package.

Altair 2 would work with vega >=1 <2. Altair 3 would work with vega >=2. Npm addresses this issue with peer dependencies but I'm not aware of any equivalent in Python.

OK, makes sense.

Another problem is Jupyterlab. They already updated to Vega-Lite 3 accidentally.

I reverted to Vega-Lite 2 in https://github.com/jupyterlab/jupyterlab/pull/5342.

I see that the docs in https://altair-viz.github.io/user_guide/display_frontends.html#display-notebook still expect users to install any version of the vega package. Should we update this and then in a week or so make a release of a new vega package with Vega-Lite 3?

a new release with Vega-Lite 3 would be really nice.

@jakevdp can I update without breaking Altair users?

can I update without breaking Altair users?

No, not unless we change install instructions to pin the vega version.

Since vega 3 is still a pre-release, why not add an ipyvega pre-release as well that uses it? Then pip would not install it unless users specifically request the prerelease version.

Oh, I didn't know we can just make a prerelease version. I'll do that.

Instructions: https://packaging.pypa.io/en/latest/version/

Done

screen shot 2018-10-25 at 10 27 17

Was this page helpful?
0 / 5 - 0 ratings

Related issues

SuperShinyEyes picture SuperShinyEyes  路  3Comments

Juan-132 picture Juan-132  路  3Comments

jtbaker picture jtbaker  路  3Comments

bmcfee picture bmcfee  路  3Comments

galloramiro picture galloramiro  路  3Comments