You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a project still using Pydantic 1 and I recently tried upgrading chromadb-client from 0.5.4.dev0 to 0.5.5.dev0, failing with an error in types.py, which uses model_fields, a feature added in Pydantic 2:
rChaoz
changed the title
[Bug]: 0.5.5 uses Pydantic 2 features while still depending on Pydantic 1+
[Bug]: v0.5.5 uses Pydantic 2 features while still depending on Pydantic 1+
Jul 11, 2024
rChaoz
changed the title
[Bug]: v0.5.5 uses Pydantic 2 features while still depending on Pydantic 1+
[Bug]: v0.5.5 uses Pydantic 2 features while depending on Pydantic 1
Jul 11, 2024
Closes#2503Closes#2137
## Description of changes
*Summarize the changes made by this PR.*
- Improvements & Bug fixes
- Support for pydantic 1.x in FastAPI server.
## Test plan
*How are these changes tested?*
- [x] Tests pass locally with `pytest` for python, `yarn test` for js,
`cargo test` for rust
## Documentation Changes
N/A
What happened?
I have a project still using Pydantic 1 and I recently tried upgrading
chromadb-client
from 0.5.4.dev0 to 0.5.5.dev0, failing with an error intypes.py
, which usesmodel_fields
, a feature added in Pydantic 2:chroma/chromadb/types.py
Lines 99 to 100 in 45aba8a
But ChromaDB depends on Pydantic 1+:
chroma/pyproject.toml
Lines 17 to 19 in 45aba8a
Versions
ChromaDB v0.5.5, ChromaDB-Client v0.5.5-dev0
Relevant log output
The text was updated successfully, but these errors were encountered: