Compose: Update jsonschema dependency

[goodspark]

Is your feature request related to a problem? Please describe.
I'm trying to install poetry and docker-compose in a virtualenv but since they depend on different jsonschema major versions they become incompatible when running together in the venv.

• poetry: >=3, <4
• docker-compose: >=2.5.1, <3

Describe the solution you'd like
docker-compose to update its jsonschema dependency to >=3, <4.

Describe alternatives you've considered
I could just put the two in different venvs. I'm lazy and just want all my tools available in a single venv so I don't have to hop around so much.

[shin-]

Looks like version 3.0.0 of jsonschema is still in alpha. We'll definitely want to wait for a stable release before we consider this change, and measure what changes are required in our codebase to work with the new version.
I'm happy to put this on my radar, but I don't expect this to be resolved for some time still. As an alternative, you may want to try using the Compose binary instead.

[goodspark]

Cool. Thanks! Defer to you what you want to do with this specific issue until then.

[chrislan815]

Version 3.0.0 of jsonschema is not in alpha anymore -- do we have plan on moving to v3.0.0?

[lsterk]

@shin- any updates on this? According to https://github.com/Julian/jsonschema , {{jsonschema==3.0.1}} is a stable release (since March 1).

This issue makes it difficult to bundle {{docker-compose}} in a library due to the strict pin on a package that is now starting to be adopted in other libraries.

[shin-]

@lsterk I'm no longer a maintainer, but the best way to get the ball rolling on this is probably to make a PR for it.