-
Notifications
You must be signed in to change notification settings - Fork 181
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
Draft7Validator(TyperError: create.<locals>.Validator.__init__() got an unexpected keyword argument 'registry' #369
Comments
Getting the same issue here - did you manage to figure out the cause? Versions for mine (in case it helps triangulate):
|
Aha - for me the culprit was apparently an older version of jsonschema that had been pulled in as a dependency by another python module. |
I am having the same problem in Ubuntu 20.04 in pipenv and poetry envs as well. Any ideas how to fix it?
|
Downgrading |
@Julian Any suggestions? |
How does one reproduce the issue being reported here? |
Running |
Should this line now also include <4.20.0? |
That produces no error here.
(and for reference:
|
Wait, now I updated jsonschema to 4.20.0 and I cannot reproduce the error. I really didn't change anything in between... |
how to slove it ? |
Hit same error
I solved it by
as per this post |
@fengs Your answer above solved my issue as well. |
I'll just note that running that sort of command is exactly the kind of mistake that's likely to have gotten you into this situation. Specifically, I claim the only way you could have broken your installation is by running that kind of command! It's true that running a similar one may get you out of it. But in Python, it is not safe to run repeated installation commands willy nilly.
|
@Julian Keep in mind that some of us develop in environments where we only have partial admin rights. Your assumption is incorrect as I did a full install, and for whatever reason, I get the error above. (Keep in mind that I've used dozens of laptops/desktops over the past 3 years and only recently experienced this issue) I'll add that I fully agree this will very likely cause versioning issues in the not-too-distant future... |
While I don't blame you as a user, my message is precisely to eliminate:
There is I claim no way this could happen. If there were, I would love to see it, and would be happy to look into it. Otherwise though, my assumption remains, I assume the only way any user could get into this state is by doing something as I say causes general poor behavior and isn't supported (namely running partial installs). |
@Julian This occurred after I did a fresh install and then installed CUDA-enabled PyTorch. |
A fresh install of *what*? That sounds precisely like you're saying you did
the thing I said causes issues.
|
Apologies for coming across as passive aggressive. I edited my comment after re-reading it and realizing I sounded like an arse. I downloaded and did a clean install of the most recent version of Anaconda. The only thing I can think of that I did that could have possibly caused an issue was from installing PyTorch and CUDA. However, I created a virtual env before doing this, so I don't think it would make the notebook completely break, right? |
(No worries, I didn't see the edit, but now I do, so now I've edited mine. No hard feelings certainly.)
But then you ran I honestly don't use Anaconda so I am no expert, but I would assume indeed that if you did run |
Please try: |
Thanks! |
Getting this error with the latest Arch package version
The text was updated successfully, but these errors were encountered: