ImportError: cannot import name 'ArgSpec' from 'inspect'

[Abhiz2411]

Things to check first

• I have searched the existing issues and didn't find my bug already reported there

• I have checked that my bug is still present in the latest release

Sqlacodegen version

2.3.0.post1

SQLAlchemy version

1.4.52

RDBMS vendor

PostgreSQL

What happened?

When I ran the command sqlacodegen postgresql://postgres:secret_pass@localhost:5432/db_name > model.py It should have created code in model.py. I researched about the error and I think it is caused because codegen.py has an import statement from inspect import ArgSpec where ArgSpec is depreciated for python 3.12.2. I am using 3.12.2 version of python

Database schema for reproducing the bug

No response

[trembel]

For me it is solved using the rc version. Try pip install sqlacodegen==3.0.0rc5, see here: #251

[rafalkrupinski]

The last stable release is from 2020 and declares requirement on python 3.8
The latest python it actually works is 3.10
I use pipx and pyenv, so no problem. uv should handle it too.

[Abhiz2411]

Thanks. Will give it a shot

…

On Wed, Jan 8, 2025 at 8:07 PM Rafal Krupinski ***@***.***> wrote: The last stable release is from 2020 and declares requirement on python 3.8 The latest python it actually works is 3.10 I use pipx and pyenv, so no problem. uv should handle it too. — Reply to this email directly, view it on GitHub <#326 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AP243TW74DMBM56MPKSXWSL2JUZ37AVCNFSM6AAAAABU2CIXGSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZXHAZTANJYHE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[sheinbergon]

@Abhiz2411 as mentioned earlier, latest 3.0.0rc5 does support python 3.12.
We are currently actively working on a stable 3.0.x release

[agronholm]

The reason I pinned this issue is because people who don't know about pre-releases keep re-reporting this.

[agronholm]

But admittedly closing it doesn't unpin it, so let's hope people coming in to report this can still find it.

[kdipippo]

Confirming I was able to find this issue when I encountered this error just now after it's been closed 13 hours ago. 3.0.0rc5 worked perfectly