RefResolver is deprecated, but replacement is unstable #1383

Hi folks,

I want to integrate jsonschema in the application I'm working on. It's a widely-used desktop application, and so I do not want it to show deprecation warnings on the console. This means that ideally I wouldn't use jsonschema.RefResolver (deprecated since 238e711), but rather use the new referencing package. However, the latter is still in beta, and its API is explicitly documented as not stable.

The current release of jsonschema seems to add referencing as a mandatory dependency. Inclusion of beta-stage packages in a package marked "Production/Stable" seems dubious.

What is the recommended approach, in cases where depending on beta-stage software is not desirable? It also feels dodgy to introduce a new package (jsonschema) to our application and immediately start using an API that is already marked deprecated.

Thanks for any guidance.