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
/Users/xyz/.local/share/uv/tools/vectorcode/lib/python3.14/site-packages/vectorcode/main.py:120: SyntaxWarning: 'return' in a 'finally' block
return return_val
Traceback (most recent call last):
File "/Users/xyz/.local/bin/vectorcode", line 4, in <module>
from vectorcode.main import main
File "/Users/xyz/.local/share/uv/tools/vectorcode/lib/python3.14/site-packages/vectorcode/main.py", line 17, in <module>
from vectorcode.common import ClientManager
File "/Users/xyz/.local/share/uv/tools/vectorcode/lib/python3.14/site-packages/vectorcode/common.py", line 15, in <module>
import chromadb
File "/Users/xyz/.local/share/uv/tools/vectorcode/lib/python3.14/site-packages/chromadb/__init__.py", line 2, in <module>
import chromadb.config
File "/Users/xyz/.local/share/uv/tools/vectorcode/lib/python3.14/site-packages/chromadb/config.py", line 1, in <module>
from pydantic import BaseSettings
File "/Users/xyz/.local/share/uv/tools/vectorcode/lib/python3.14/site-packages/pydantic/__init__.py", line 437, in __getattr__
return _getattr_migration(attr_name)
File "/Users/xyz/.local/share/uv/tools/vectorcode/lib/python3.14/site-packages/pydantic/_migration.py", line 304, in wrapper
raise PydanticImportError(
...<3 lines>...
)
pydantic.errors.PydanticImportError: `BaseSettings` has been moved to the `pydantic-settings` package. See https://docs.pydantic.dev/2.12/migration/#basesettings-has-moved-to-pydantic-settings for more details.
For further information visit https://errors.pydantic.dev/2.12/u/import-error
I did uv python install 3.13, reinstalled VectorCode, and it now works.
This is definitely on my TODOs. It's just a matter of priorities.
I'd prefer to solve this after decoupling from chromadb 0.6.3 (#282 is almost done, I had some new ideas about the db abstraction design, so I decided to put it off). Since chromadb 0.6.3 was released before python3.14, I don't think it's a very good idea to lift the python version constraint. Once I finish the refactoring of the database stuff and enable support for multiple database backends (chroma 1.x and more), it'll then make sense to actually enable python 3.14.
It's also worth noting that the last time when I tried to run VectorCode with python3.14 locally (#296), some of the dependencies wouldn't install because they weren't ready for python3.14. From that perspective, it's not a VectorCode-only issue and may require certain upstream packages to update their metadata/codebase.
Reacted by Jay Sitter, Gregory M. Kapfhammer and Cenk Kılıç
Activity
Davidyz commentedon Dec 26, 2025
This is definitely on my TODOs. It's just a matter of priorities.
I'd prefer to solve this after decoupling from chromadb 0.6.3 (#282 is almost done, I had some new ideas about the db abstraction design, so I decided to put it off). Since chromadb 0.6.3 was released before python3.14, I don't think it's a very good idea to lift the python version constraint. Once I finish the refactoring of the database stuff and enable support for multiple database backends (chroma 1.x and more), it'll then make sense to actually enable python 3.14.
It's also worth noting that the last time when I tried to run VectorCode with python3.14 locally (#296), some of the dependencies wouldn't install because they weren't ready for python3.14. From that perspective, it's not a VectorCode-only issue and may require certain upstream packages to update their metadata/codebase.