I’m unsure as to how well this is known, but just in case it helps someone else:
Currently when building python3.9 for the common workflows package, there are some steps to be aware of.
If python>=3.10, you will have to install 3.9. I did this from source (Python-3.9.18), and hit a snag with the database. no module named '_sqlite3' would appear when trying to set up a profile (or any other db access)
Solved by installing sqlite3-dev (sudo apt install libsqlite3-dev) and then building with: ./configure --enable-loadable-sqlite-extensions --with-ensurepip=install && make -j 4 && sudo make altinstall
Note, I’m building here with --with-ensurepip=install (installs pip), and sudo make altinstall (does not override the main python version)
I recreated the venv after this, though I’m not sure that’s neccessary.
Thanks @ljbeal! Good to know about these installation hurdles. What OS are you running? I’ll see about adding these notes to a troubleshooting section in the docs.
Progess is coming along just fine, jobs can be submitted and the CI is passing (though it’s more of a framework than a full test suite).
I wanted to get the common workflows functional again before pushing, however I’m running into issues getting the base common workflows running. Possibly more to come on that front depending on how my next few experiments go.
So in short, the plugin works, but I’m not convinced that the workflows do