Skip to content
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

In Colab: Connecting fails: "got an unexpected keyword argument 'bind'" #227

Open
jsmorph opened this issue Feb 2, 2023 · 6 comments
Open

Comments

@jsmorph
Copy link

jsmorph commented Feb 2, 2023

Connecting like

%sql mysql+pymysql://{user}:{password}@{host}/shared

now produces:

__init__() got an unexpected keyword argument 'bind'
Connection info needed in SQLAlchemy format, example:
               postgresql://username:password@hostname/dbname
               or an existing connection: dict_keys([])

This error started happening in the last 24 hours.

Ideas?

@kpgaffney
Copy link

I'm not sure what's causing this, but it looks like it's related to SQLAlchemy version 2.0.0. As a temporary workaround, I added !pip install SQLAlchemy==1.4.46 before %load_ext sql, which fixed the problem.

@jsmorph
Copy link
Author

jsmorph commented Feb 3, 2023

Thanks very much for the quick fix.

FWIW, I'm now pinning versions like this in Colab:

!pip install SQLAlchemy==1.4.46
!pip install PyMySQL==1.0.2 # or whichever
!pip install ipython-sql==0.4.1

@rwarren
Copy link

rwarren commented Feb 14, 2023

Same problem here, but when I install SQLAlchemy 1.4.46 it does not help. In my case I'm running a local jupyterlab (version 3.6.1).

image

@tjerkw
Copy link

tjerkw commented Feb 16, 2023

Same issue, pinning sqlAclhemny or ipython-sql does not work.

@jsmorph
Copy link
Author

jsmorph commented Feb 16, 2023

@tjerkw and @rwarren, did you restart the runtime after the pinned pip installs? When I do these installs and then restart the runtime, things work. (Menu: Runtime -> Restart runtime.)

@rwarren
Copy link

rwarren commented Feb 16, 2023

@jsmorph I thought I had restarted, but apparently not! After a fresh reboot today, this is is working perfectly fine after installing SQLAlchemy==1.4.46. 👍

pmfischer pushed a commit to pmfischer/ipython-sql that referenced this issue Sep 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants