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
Backport bug fixes for a 4.2.1 release #2827
Conversation
* Disable uri-reference format check. Consistently use same validator across codebase * Remove validation in SchemaInfo as not used anywhere and it referenced the wrong jsonschema draft * Add compatibility for older jsonschema versions * Improve comments * Simplify validate_jsonschema
Thanks for working on this @jtilly ! Regarding my previous comment, I think I made a more accurate one here #2817 (comment):
I guess between the two approaches it would make more sense to cherrypick the relevant commits into a separate branch (as you have here) and do a 4.3 release from that rather than trying to get the main branch in the right order. As I mentioned in that comment, I do see advantage with a 4.3 release, but I don't have the bandwidth to put into work or review on that myself and would rather focus my efforts towards 5.0. Having that said, if someone else is willing to review, I definitely don't have anything against there being a 4.3/4.2.1 release with the most important bugfixes. I would also like to draw your attention to #2599 (reply in thread), which mentions not all of the maintainers have the required permissions to make a PyPI release, so if you are hoping to make a quick 4.3 release while waiting for 5.0, I am not sure if that will happen and it might be more likely that they both come out at a similar time (but that's a bit of speculation from my side, just wanted you to be aware of these caveats). |
That was my hope indeed 😁 In any case, I wanted to give it a try -- please let me know if there are any other bug fixes that should be backported. |
Would love a patch for #2771 soon, to avoid forcing |
Not a patch, but as was found here: #2794, to avoid pinning
|
I think it is a good idea to prepare for a hotfixed version of altair 4.2. I also would like to include some warnings of features that will be removed in altair 5. |
* DOC: remove unused section * Disable uri-reference format check in jsonsschema (vega#2771) * Disable uri-reference format check. Consistently use same validator across codebase * Remove validation in SchemaInfo as not used anywhere and it referenced the wrong jsonschema draft * Add compatibility for older jsonschema versions * Improve comments * Simplify validate_jsonschema * Replace `iteritems` with `items` due to pandas deprecation (vega#2683) * Add changelog entry. * Bump version. * Run black and flake8. * Pin selenium in CI. Co-authored-by: Jake VanderPlas <jakevdp@google.com> Co-authored-by: Stefan Binder <binder_stefan@outlook.com> Co-authored-by: Joel Ostblom <joelostblom@users.noreply.github.com>
* include an altairfuturewarning * deprecate vega 5 wrappers and render function * deprecate vegalite 3 wrappers and render function * use AltairDeprecationWarning * fix typo in v5 warning * remove mentioning alternative for vega wrappers * Backport bug fixes for a 4.2.1 release (#2827) * DOC: remove unused section * Disable uri-reference format check in jsonsschema (#2771) * Disable uri-reference format check. Consistently use same validator across codebase * Remove validation in SchemaInfo as not used anywhere and it referenced the wrong jsonschema draft * Add compatibility for older jsonschema versions * Improve comments * Simplify validate_jsonschema * Replace `iteritems` with `items` due to pandas deprecation (#2683) * Add changelog entry. * Bump version. * Run black and flake8. * Pin selenium in CI. Co-authored-by: Jake VanderPlas <jakevdp@google.com> Co-authored-by: Stefan Binder <binder_stefan@outlook.com> Co-authored-by: Joel Ostblom <joelostblom@users.noreply.github.com> * include note in releases change log Co-authored-by: Jan Tilly <jan.tilly@quantco.com> Co-authored-by: Jake VanderPlas <jakevdp@google.com> Co-authored-by: Stefan Binder <binder_stefan@outlook.com> Co-authored-by: Joel Ostblom <joelostblom@users.noreply.github.com>
Hi everyone,
I'm a big fan of altair! Thanks for all your work on this.
I've read #2588, #2768 and related issues and I was wondering if you'd be willing to make a 4.2.1 (or 4.3.0) release with bug fixes as long as I do all the work on it? (Or almost all of the work, because based on #2793, one of you would still need to make the actual PyPI release).
In this PR, I'm backporting
iteritems
withitems
#2683and I bumped the version number and added a changlog entry.
I'm happy to backport more PRs that are fixing critical issues (if desired).
The PR is using
v4.2.X
as base branch.Test suite is ✅ (after installing
altair_saver
and'vega-lite-cli<5'
so that no tests are skipped).In #2588 (reply in thread), @joelostblom writes that
I'm not exactly sure what you mean by that and I would hope that it's fine to not have these bug fix commits in the correct order in the main branch.
If you're saying this is not worth the effort, feel free to close the PR.