Skip to content
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

Update constraint on jsonschema library version #113

Closed
1 task done
nvn-nil opened this issue May 1, 2024 · 0 comments · Fixed by #114
Closed
1 task done

Update constraint on jsonschema library version #113

nvn-nil opened this issue May 1, 2024 · 0 comments · Fixed by #114

Comments

@nvn-nil
Copy link

nvn-nil commented May 1, 2024

Feature request

  • I've searched the list of existing issues

The constraint on the jsonschema library version of ~=4.4.0 (==4.4.*) is too tight and incompatible with some open-source libraries' latest versions.

I'm trying to set up Jupyter in WindQuest so that python manage.py shell_plus --notebook works, but installing the latest version of the notebook fails with:

Using version ^7.1.3 for notebook

Updating dependencies
Resolving dependencies... (7.0s)
...
...
Because no versions of twined match >0.5.1,<0.5.2 || >0.5.2,<0.5.3 || >0.5.3,<0.5.4 || >0.5.4,<0.6.0
 and twined (0.5.1) depends on jsonschema (>=4.4.0,<4.5.0), twined (>=0.5.1,<0.5.2 || >0.5.2,<0.5.3 || >0.5.3,<0.5.4 || >0.5.4,<0.6.0) requires jsonschema (>=4.4.0,<4.5.0).
    And because twined (0.5.2) depends on jsonschema (>=4.4.0,<4.5.0)
 and twined (0.5.4) depends on jsonschema (>=4.4.0,<4.5.0), twined (>=0.5.1,<0.5.3 || >0.5.3,<0.6.0) requires jsonschema (>=4.4.0,<4.5.0).
    And because octue (0.52.0) depends on twined (>=0.5.1,<0.6.0)
 and twined (0.5.3) depends on jsonschema (>=4.4.0,<4.5.0), octue (0.52.0) requires jsonschema (>=4.4.0,<4.5.0).
    And because notebook (>=7.1.3,<8.0.0) requires jsonschema (>=4.17.3) (2), notebook (>=7.1.3,<8.0.0) is incompatible with octue (0.52.0)
    So, because wq depends on both octue (0.52.0) and notebook (^7.1.3), version solving failed.

These libraries have older releases, but it'd be great not to have to pin other libraries to older versions.

@cortadocodes cortadocodes linked a pull request May 1, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants