Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Altair 5 release candidate info and feedback #2937

Closed
mattijn opened this issue Mar 1, 2023 · 6 comments
Closed

Altair 5 release candidate info and feedback #2937

mattijn opened this issue Mar 1, 2023 · 6 comments

Comments

@mattijn
Copy link
Contributor

mattijn commented Mar 1, 2023

Thanks for your interest in the release candidate for Vega-Altair 5!

If you have any general feedback on the direction of the release candidate, please feel free to share it here (e.g. on the new method-based syntax for setting encoding channel options). If you run into specific problems, please open individual issues for those.

Before you get started, make sure that you read the release notes to see what has changed and take a tour of the revamped documentation pages to learn more about the new features.


Please take note of the following limitations present in the release candidate, which we are working to resolve before the official release of Altair 5.0.0.

  • Downstream dependencies such as altair_data_saver, altair_viewer and altair_saver are not yet ready for Altair 5. If you are dependent on these, please wait.

You can install the release candidate of version 5 using the following pip-command:

pip install altair==5.0.0rc3
@firasm
Copy link

firasm commented Mar 2, 2023

This is very exciting!! Thank you to everyone involved 🥳🥳🤩🤩

@philippjfr
Copy link

Great work on this! One quick question, what's the timeline for the release? We're going to push out a Panel 0.14.4 patch release with compatibility for selections with older and newer vega-lite/altair versions. I'd like to show the new altair API (.add_params) in the docs but if it's a few weeks out I'd probably postpone the docs update.

@mattijn
Copy link
Contributor Author

mattijn commented Mar 2, 2023

Its not fixed, but a few weeks sounds likely.

@philippjfr
Copy link

Thank you, might hold off on the documentation updates for now then.

@AdamCiuris
Copy link

thank you for docs additions

@joelostblom
Copy link
Contributor

Closing this as we have released v5!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants