When running a mitosis experiment (ARA-Plumes), Ike got the following error:
File "/Users/Malachite/opt/anaconda3/envs/ARA-plume-exp/lib/python3.11/site-packages/mitosis/__init__.py", line 238, in _verify_variant_name
df = pd.read_sql(select(tb), eng)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/Malachite/opt/anaconda3/envs/ARA-plume-exp/lib/python3.11/site-packages/pandas/io/sql.py", line 706, in read_sql
return pandas_sql.read_query(
^^^^^^^^^^^^^^^^^^^^^^
File "/Users/Malachite/opt/anaconda3/envs/ARA-plume-exp/lib/python3.11/site-packages/pandas/io/sql.py", line 2736, in read_query
cursor = self.execute(sql, params)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/Malachite/opt/anaconda3/envs/ARA-plume-exp/lib/python3.11/site-packages/pandas/io/sql.py", line 2668, in execute
raise TypeError("Query must be a string unless using sqlalchemy.")
TypeError: Query must be a string unless using sqlalchemy.
My guess is a certain version of pandas' read_sql function expects a sqlalchemy engine if its given a sqlalchemy select statement. But sqlalchemy's create_engine may create a sqlite3 engine directly, instead of one that pandas recognizes as sqlalchemy.
When running a mitosis experiment (ARA-Plumes), Ike got the following error:
My guess is a certain version of pandas'
read_sql
function expects a sqlalchemy engine if its given a sqlalchemy select statement. But sqlalchemy'screate_engine
may create a sqlite3 engine directly, instead of one that pandas recognizes as sqlalchemy.