The 3.0 release of this library introduced a number of breaking changes in the API. We've written a migration guide here: https://pyairtable.readthedocs.io/en/3.0.0/migrations.html
If you see errors like this:
'Table' object has no attribute 'url''Base' object has no attribute 'webhooks_url''Model' object has no attribute 'get_model'
...or something like it, then you probably have an unpinned dependency in your project. You should update your project's dependencies to be pinned to version 2.x until you have a chance to upgrade. Whether you use setuptools, pipenv, poetry, or just requirements.txt, a version specifier like pyairtable~=2 or pyairtable>=2,<3 should ensure you stay on a compatible version until you're ready to upgrade.
(This issue should remain open and pinned to the top of the issues list for some time after the 3.0 release.)
The 3.0 release of this library introduced a number of breaking changes in the API. We've written a migration guide here: https://pyairtable.readthedocs.io/en/3.0.0/migrations.html
If you see errors like this:
'Table' object has no attribute 'url''Base' object has no attribute 'webhooks_url''Model' object has no attribute 'get_model'...or something like it, then you probably have an unpinned dependency in your project. You should update your project's dependencies to be pinned to version 2.x until you have a chance to upgrade. Whether you use setuptools, pipenv, poetry, or just requirements.txt, a version specifier like
pyairtable~=2orpyairtable>=2,<3should ensure you stay on a compatible version until you're ready to upgrade.(This issue should remain open and pinned to the top of the issues list for some time after the 3.0 release.)