sqlite3 error

pfr

I've installed kb-manager using py37-pip as guided by the instructions on the github page. I've run into an error which appears to be related to sqlite3.

Besides what I've reported on the github issue I've also done pkg_admin rebuild & pkg_admin rebuild-tree as instructed by Jay and the error persists.

I'm a little perplexed by the fact that sqlite3-3.26.0 was already installed (in base?) and when I installed sqlite3-3.33.0 running sqlite3 --version still came back with v3.26.0. Anyhow, this leads me to believe it moght not be an issue with which version is installed, or perhaps it is if v3.33.0 cant be found.

Lastly, where is PYTHONPATH usually set? It isn't in my ~/.profile ... should it be?

Any help or advice is greatly appreciated 😃

rvp

EDIT: use which -a binary on NetBSD. whereis -ab binary on FreeBSD.

pfr I'm a little perplexed by the fact that sqlite3-3.26.0 was already installed (in base?) and when I installed sqlite3-3.33.0 running sqlite3 --version still came back with v3.26.0.

Run: which -a sqlite3. You should see 2 binaries, the first of which is what's being used. Adjust PATH, or, remove the binary pkg version.

I think the root cause of your problems is your not having the Python sqlite bindings library installed. Uninstall the extra sqlite package first, and then install the appropriate python3 sqlite3 library: pkgin search sqlite | fgrep py3. (Or maybe do the same thing using pip--I dunno much about pip.)

pfr

rvp Uninstall the extra sqlite package first, and then install the appropriate python3 sqlite3 library: pkgin search sqlite | fgrep py3

Thanks, that solved it. Just needed py37-sqlite3. I don't understand much when it comes to python and the fact that there are different versions needed to be installed at once confuses me. Why can't py37 replace py27, supporting all the packages previously requiring py27?

FYI > kb-manager

pfr Why can't py37 replace py27, supporting all the packages previously requiring py27?

Because a lot of upstream projects did not adapt their code to work with py3. Reasons for this may vary and every example would probably have theirs.

py3 is not backwards compatible with py2.

nia

The different versions of Python 3 aren't backwards compatible with each other either - e.g. some Python version added an "async" keyword which broke any code using "async" as a variable name.

Currently 3.6, 3.7, 3.8, and 3.9 are all supported by Python upstream. So, in pkgsrc we let you choose so your code doesn't unexpectedly break, you can test with different versions, etc.

nia welcome to the snakepit 😉

rvp

pin welcome to the snakepit

🤣+1

pfr

So I just completed a clean install of NetBSD 9.1-STABLE and rather than install py37 I tried this with py38 which is already installed as a dependency for other packages.

This time I installed py38-pip py38-sqlite3 pkg_alternatives however when I runpip install -U kb-manager I get ksh: pip: not found

I'd rather not install another version of python if avoidable. Any idea whats wrong here?

rvp

pfr Any idea whats wrong here?

Always install pkg_alternatives first so that it can be used by other packages. Un-install py38-*; re-install.

pfr

rvp DoH! thanks for reminding me 👍️