altair v4.2.1 without jsonschema upper bound

[jtilly]

Closes #42

This PR removes the upper bound on jsonschema for 4.2.1. This PR should merged instead of #42.

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[joelostblom]

Just a note that there will likely be a 4.2.2 release coming in a few days too that fixes the jsonschema issue vega/altair#2857 (comment)

[jtilly]

Should we then add a jsonschema >=4.3.0 to 4.2.1 for now?

[joelostblom]

I think for 4.2.2 at least yes. Maybe we could even skip this 4.2.1 release in conda and wait for 4.2.2?

[jtilly]

I interpreted vega/altair#2857 (comment) as meaning that jsonschema >=4.3.0 would work with 4.2.1. Am I reading that wrong?

Maybe we could even skip this 4.2.1 release in conda and wait for 4.2.2?

I would suggest to just merge this with a reasonable constraint and keep pypi and conda-forge releases in sync.

[binste]

Please note that the jsonschema version number 4.3.0 in that issue is wrong. The compatbility is as follows and therefore this PR should be adjusted to jsonschema>=4.5.0 for Altair 4.2.1:

• Altair 4.2.0 works with jsonschema >=3,<4.17 (just tested this locally to make sure)
  • jsonschema 4.17 introduced format validation on schemas which causes an issue which is fixed in Altair 4.2.1
• Altair 4.2.1 works with jsonschema >=4.5 (just tested this locally to make sure)
  • Altair 4.2.1 requires the FORMAT_CHECKER attribute on validator classes which was only introduced in jsonschema 4.5
• Altair 4.2.2 would work with jsonschema >= 3.0

[joelostblom]

I'm ok to merge this with the correction @binste mentioned above

[binste]

Please wait with the merge, I need to check something

[binste]

So many version numbers flying around :) Found the correct release of jsonschema which introduced the FORMAT_CHECKER attribute on the validator classes, it's 4.5.0

Updated my comment above. What we want is jsonschema>=4.5.0 for Altair 4.2.1:

Compatibility looks as follows:

• Altair 4.2.0 works with jsonschema >=3,<4.17 (just tested this locally to make sure)
  • jsonschema 4.17 introduced format validation on schemas which causes an issue which is fixed in Altair 4.2.1
• Altair 4.2.1 works with jsonschema >=4.5 (just tested this locally to make sure)
  • Altair 4.2.1 requires the FORMAT_CHECKER attribute on validator classes which was only introduced in jsonschema 4.5
• Altair 4.2.2 would work with jsonschema >= 3.0

Sorry for any confusion.

[ocefpaf]

@jtilly do you still need this PR to be merged?

[jtilly]

@jtilly do you still need this PR to be merged?

No, thank you. I think 4.2.2 is enough.