Arch Linux

rael86

Member

Registered: 2017-02-02

Posts: 4

Python still looking for 3.6 libraries

Hello, I just upgraded my system with

sudo pacman -Syu

After this upgrade, anytime I try to run python scripts I get the following:

python3: error while loading shared libraries: libpython3.6m.so.1.0: cannot open shared object file: No such file or directory

this happens both if I run python inside or outside a virtualenv.

However, if I run

 python3 --version

outside of a virtualenv or in a newwly created virtualenv I get the following output:

Python 3.7.0

while if I run it inside a virtualenv that was created before the upgrade, I get:

python3: error while loading shared libraries: libpython3.6m.so.1.0: cannot open shared object file: No such file or directory

looks like my system is a bit confused between python3.6 and python3.7, any idea on how to fix this?

eschwartz

Fellow

Registered: 2014-08-08

Posts: 4,097

Re: Python still looking for 3.6 libraries

You need to recreate the virtualenv when python itself is updated...

---

Managing AUR repos The Right Way -- aurpublish (now a standalone tool)

szebenyib

Member

From: LHBP

Registered: 2011-10-18

Posts: 70

Re: Python still looking for 3.6 libraries

Thanks! I removed the complete virtualenv by a simple rm then recreated it. This has solved the issue.

johnnynyquist

Member

Registered: 2016-01-25

Posts: 27

Re: Python still looking for 3.6 libraries

Thanks for this explanation- this helped me as well- but I am confused. Doesn't this defeat the entire purpose of virtualenv? I thought the whole point was that your system could change but your environment would not get interrupted..

Trilby

Inspector Parrot

Registered: 2011-11-29

Posts: 30,410

Website

Re: Python still looking for 3.6 libraries

https://wiki.archlinux.org/index.php/Py … n_versions\

Note that virtualenv != venv

Last edited by Trilby (2018-10-29 22:44:50)

---

"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman