-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sql code is broken #70
Comments
Looks like SQLAlchemy has changed their interface a bit: https://docs.sqlalchemy.org/en/13/core/interfaces.html#sqlalchemy.interfaces.PoolListener For the time being I recommend installing an older version of SQLAlchemy until I port the code to the latest version. |
Alright, a quick look at the code shows that PoolListener was used as a hack for detecting certain features of sqlite. So another option is to just remove the offending code, that is, the broken import, the definition of the _SQLitePatch class and the line where that class is used. I have no idea if anything else is broken too, down the road. I wrote this back when SQLAlchemy was still below 1.0 so more features could be gone. :( |
The PoolListener logic is roughly equivalent to the Event system now, as far as I see it. The code snippet from here should do the same thing like your |
Another workaround for now would also be using an older version of SQLAlchemy.
|
when importing the
winappdbg.sql
module I get an crash:I installed the winappdbg version from current head, running on python 2.7 and sqlalchemy is present (SQLAlchemy==1.4.13)
The text was updated successfully, but these errors were encountered: