Closed jwebster-LANL closed 1 year ago
It looks like SQLA 1.4 is a bridge version between 1.3 and 2.0, and has moved some things around. sqlalchemy <= 1.3.24
might work.
It looks like SQLA 1.4 is a bridge version between 1.3 and 2.0, and has moved some things around.
sqlalchemy <= 1.3.24
might work.
I can confirm that sqlalchemy 1.3.24 works.
With a fresh installation of miniconda w/Python 3.8, the following is successful
$ conda config --add channels conda-forge
$ conda config --set channel_priority strict
$ conda update -n base -c defaults conda
$ conda create -n pisces python=3.8
$ conda activate pisces
$ pip install pisces sqlalchemy==1.3.24
$ python
>>> import pisces
not to be a pest, but will pisces' aversion to sqlalchemy=1.4 be fixed anytime soon? A lot of packages are trying to install/upgrade to 1.4 these days, and forcing 1.3.24 is getting to be a bit of work.
Seriously though... what would it take to get pisces to play nice with sqlalchemy 1.4? 2.0 appears to be in beta...
Looks like there's an error when importing a new install of pisces. The newest version of sql-alchemy doesn't seem to have the sqlalchemy.ext.declarative.api module anymore