Avoid using relative imports

[OlivierBinette]

I'm getting issues with pyairtable:

I noticed that relative imports are being used, which seems to be the root of the issue in my case. Relative imports should be avoided in packages:

Relative imports for intra-package imports are highly discouraged. Always use the absolute package path for all imports. Even now that PEP 328 is fully implemented in Python 2.5, its style of explicit relative imports is actively discouraged; absolute imports are more portable and usually more readable.

pyairtable/pyairtable/__init__.py

Lines 3 to 6 in 34eb78e

	from .api import Api, Base, Table
	from .api.enterprise import Enterprise
	from .api.retrying import retry_strategy
	from .api.workspace import Workspace

[adamhetherington-dmi]

I'm experiencing the same issue, scripts are failing as a result

[bkolasa]

The same for me

[mesozoic]

Thanks for the report! This is the same as #411, a bug in pydantic 2.10.0 and 2.10.1. It was fixed in pydantic 2.10.2. Relative imports are discouraged (and I'll cut a branch to fix them) but they're a red herring here.

Try pinning your project's dependencies to either pydantic>=2,<2.10 or pydantic>=2.10.2,<3. If you still get that error, a minimal code snippet that reproduces the problem would help a lot.