Thanks @ZhengrongTao and @grahamjlinn ,
I have narrowed down the cause to the problem, which is unfortunately a major bug for anyone trying to use a version of the LBT plugin older than 2 weeks ago.
I do not yet know how I’m going to solve it for everyone using an older plugin except to say “update to the latest version.” I was planning to release LBT 1.10 today so this will be the solution for a lot of people. But it is looking like I will probably need to go through all of the Food4Rhino installers before LBT 1.10 and change them if I want them to work. And using the LB Versioner to go back to any release before last Friday February the 13th (LBT v1.9.48) will give you a broken plugin that must be fixed via CLI command, either using the one that you used, @grahamjlinn , or by force installing a specific version of Pydantic and queenbee like @amanjayedi did here:
The primary reason for the bug is that we updated to Pydantic 2.0 two weeks ago. I had though that we set everything up to make the transition smooth but it seems one of the links between packages in our dependency tree used an >= operator instead of ==. Long story short, this means that people can end up with an installation of Pydantic 2.0 but with older versions of LBT Python libraries, which are incompatible with Pydantic 2.0. This causes exceptions to be raised for anything using the Ladybug Tools libraries via CLI. This includes the LB Versioner but also includes all of the recipes.
Needless to say, I just fixed the >= operator now such that future updates of Pydantic will never cause this issue again. At this point, I think I am going to plow ahead with the LBT 1.10 release in order to give everyone a solid solution. Then, I’ll probably go back and fix all of the old Food4Rhino installers so that people still get a working version of the plugin with these installers (as long as they do not run the LB Versioner).
I will keep you posted.