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
'uri_template' distribution was not found and is required by jsonschema
with newer versions of jsonschema
#825
Comments
Just to make sure: how dandi-cli was installed? |
Afaik https://github.com/dandi/dandischema/blob/master/setup.cfg#L30 should have taken care about installing those dependencies but may be something changed in dandi schema extra depends recently - didn't check yet |
dandi/dandi-cli#825 Package-Manager: Portage-3.0.30, Repoman-3.0.3 Signed-off-by: Horea Christian <chr@chymera.eu>
dandi/dandi-cli#825 Package-Manager: Portage-3.0.30, Repoman-3.0.3 Signed-off-by: Horea Christian <chr@chymera.eu>
@yarikoptic it's installed via the system package manager, which has been distributing up-to-date versions of dandi since October. With newer versions of jsonschema the dandi CLI no longer fails with:
but with
The current solution we rely on is to use Any ideas? |
@TheChymera Are you saying that your system package manager is installing jsonschema 4.x when installing dandi? That seems wrong, since hdmf (a dependency of pynwb) requires |
@jwodder well, yes, it does, but that's because I told it to. The DANDI stack on Gentoo is maintained by me, so if anything is wrong I can fix it quite rapidly. I actually checked in with HDMF upstream a while ago (since |
@TheChymera I don't know about pynwb, but dandi doesn't care. However, dandischema requires |
@jwodder thanks again for clarifying this. It was indeed a name mix-up after the jsonschema update. Solved as of: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e7963135d008f2a75f05b51d2ed4dcde078f5fcc |
Should we add a dependency constraint for jsonschema?
I get the following error with
=jsonschema-4.1.0
but not=jsonschema-3.2.0
.The text was updated successfully, but these errors were encountered: