-
Notifications
You must be signed in to change notification settings - Fork 70
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
BaseSettings has moved to a new package pydantic-settings #312
Comments
I am hitting the same problem. The issue seems to be that with Pydantic V2 some API breaking changes have been introduced. Nevertheless, QCElemental lists this Line 34 in 7b04890
|
Agreed, I need to add the pydantic<2.0 restriction generally and mint a new version. I did do a new build number in conda with the restriction, but that doesn't help the src and pip usages. Thanks for the ping. |
Has this been resolved in the current conda build? |
The conda package v0.26.0 as of an hour ago works in the presence of pydantic v1 or v2. It's still using the v1 API, so I'll leave this open for the v2 migration and for general info. |
great, thank you for the fix! |
- pyscf < 2.3 in order to keep bridge test passing - pydantic < 2 because of MolSSI/QCElemental#312 - adding qcelemental >= 0.26 instead wasn't working
Describe the bug
QCElemental/qcelemental/util/autodocs.py
Line 6 in 7b04890
BaseSettings
has moved to a new packagepydantic-settings
https://docs.pydantic.dev/latest/migration/#basesettings-has-moved-to-pydantic-settings
https://github.com/pydantic/pydantic-settings
**To Reproduce
conda listNot used.Can't currently run:
python -c "import qcelemental as qcel; print(qcel.__file__, qcel.__version__)"
Expected behavior
Be able to import qcelemental
The text was updated successfully, but these errors were encountered: