Drop support for old jsonschema (to drop need to parse version strings)
Motivation and Context
Looking at https://github.com/conda-forge/event-model-feedstock/pull/46 the failures are because our tests use distutils which were removed in py312. The first commit changes to use packgaing.version.parse instead. However, we only need to check version strings to support jsonschema < 3 which at this point is almost 5 years old so I think we can safely require a newer version of jsonschema.
If changing the dep pinning in too aggressive I can drop the second commit.
Description
Drop support for old jsonschema (to drop need to parse version strings)
Motivation and Context
Looking at https://github.com/conda-forge/event-model-feedstock/pull/46 the failures are because our tests use
distutils
which were removed in py312. The first commit changes to usepackgaing.version.parse
instead. However, we only need to check version strings to support jsonschema < 3 which at this point is almost 5 years old so I think we can safely require a newer version ofjsonschema
.If changing the dep pinning in too aggressive I can drop the second commit.
attn @ZLLentz
How Has This Been Tested?