You are not logged in.
Hi,
I recently upgraded my whole system and it seems that python 3.3 was completely removed and replaced with 3.4.
I'm ok with that since it's the expected workflow. Except that when I'm in my virtualenv I can no longer use python 3.3.
⌁ [hellsing:/ … /xxxxx] [dj1.6venv] branch(+0/-0)+ ± python
python: error while loading shared libraries: libpython3.3m.so.1.0: cannot open shared object file: No such file or directoryIs there a simple way I can modify this behaviour and still keep python 3.3 on my computer ?
Or do I have to replace my virtualenv with a 3.4 venv ?
Offline
Have you read https://wiki.archlinux.org/index.php/Virtualenv ?
Offline
Of course. I know and understand how a virtualenv works. But the upgrade just replaced my virtualenv-3.3 command with virtualenv-3.4 which broke my developpment.
Now I had to recreate a new virtualenv with 3.4 and install my requirements again. Even if that sounds like a good idea at first, I'm the only one using Archlinux in the dev team and so the only one who have python3.4 now. That's why I asked if somebody knew how I could keep python3.3...
Offline
Even if that sounds like a good idea at first, I'm the only one using Archlinux in the dev team and so the only one who have python3.4 now. That's why I asked if somebody knew how I could keep python3.3...
There are python 3.1 and 3.2 packages. Maybe using python 3.3 like this would help?
https://aur.archlinux.org/packages/python31/
https://aur.archlinux.org/packages/python32/
Offline
Same Issue:
As far as I understand the Python 3.3 virtual env build was using a share library which is no longer existant (since the main build was upgraded to 3.4). Any idea what the best way to deal with this is?
Offline
dejy,
there's now an AUR package that builds python 3.3 , https://aur.archlinux.org/packages/python33/ .
You should decide whether you do need to have python 3.3 available, if so use that package.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline