Update for sqlalchemy >= 1.4.0

[sbrun]

What's the problem this feature will solve?
Faraday is not compatible with SQLAlchemy version >= 1.4.0. This Python module has already been uploaded in Debian and will be soon in kali-rolling

Describe the solution you'd like
Please update faraday to be compatible with sqlalchemy >=1.4.0

Additional context
FTR the Python module nplusone is also not compatible with sqlalchemy >= 1.4.0

[aenima-x]

@sbrun do you have an ETA of when kali will upgrade?

[sbrun]

I have no ETA but the sooner the better.
SQLAlchemy >=1.4 is already in kali-dev and its "migration" into kali-rolling is blocked automatically because of Faraday. So Faraday is not broken in kali-rolling and will not be broken.
I think the changes in Faraday are not simple.

[aenima-x]

@sbrun This is a big change for us, we are adding this to our roadmap.
But its not easy change, can you give me an estimate or a deadline of when you need this fixed?

[sbrun]

I plan to embed the "old" version of SQLAlchemy in Faraday in the Kali package to give you time to upgrade Faraday.
So I really have no deadline for you.

[aenima-x]

@sbrun Great, thank you.
This will give us time to finish some big changes we are making.
We will fix this as soon as we can.

I'll leave this issue open to let you know when its done.

[ignaciosoto93]

Hi @sbrun, @aenima-x,

This issue has been open for over 4 years. Checking the current requirements.txt, the constraint remains:

SQLAlchemy>=1.2.0,<1.4.0

Current status: Not implemented. The codebase has ~131 occurrences of .query() patterns across 26 files that would need migration to SQLAlchemy 2.0 style.

Is this upgrade still on the roadmap? SQLAlchemy 1.3.x is now significantly outdated, and the 2.0 migration would also require updating:

• Flask-SQLAlchemy (currently <=2.5.1)
• marshmallow-sqlalchemy
• nplusone (or replacing it)

If this remains a priority, it would be helpful to know if there's a timeline or if community contributions would be welcome for this migration.