-
-
Notifications
You must be signed in to change notification settings - Fork 109
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
BUG #219
Comments
I'm getting this error as well. Fresh install this morning. |
@profile-55 @Daniel-Ross Forks do exist of Rocketry with pydantic.v1 shoe horned into the imports and a couple of PRs exist in fixing the overarching issue. But theres still ongoing work and Miksus is busy with other things at the moment. If you need a quick fix, tie pydantic to v1.10.10 in your requirements.txt files and re-install pydantic in your venvs
If you desperately need to use pydantic v2 (like with a requirement for another module you're using) then maybe take a look at one of the forks someone has done in the short term. |
Is there any chance that this will be fixed in the near future? |
@MMartin09 The blocker in this is the RedBird PR. Once thats finished then theres probably just some tweaks to do to the Rocketry PR. I just haven't really had time to look at the RedBird PR. Its quite difficult to migrate due to the variety of ways Pydantic has been used that aren't compatible with v2 and each issue requires a lot of digging to find an alternate solution. I'm quite tied up with work so haven't really had time to look further and I expect I should be busy for another month or so. I'll try continue the PR when I can, but when its finished I'm not sure when Miksus will be around to review the PR. Probably not going to be a quick solution in the short term from my end. |
Okay great. Thanks for the detailed answer! |
Can't start example from documentation!
Use "Rocketry" version 2.5.1, installed with "Poetry"
Error: raise PydanticUserError('
const
is removed, useLiteral
instead', code='removed-kwargs')Screenshots
The text was updated successfully, but these errors were encountered: