Project

General

Profile

Bug #3543

[i686/python]: ModuleNotFoundError when attempting to execute any python dependent package

doolio - 4 months ago - . Updated 3 months ago.

Status:
forwarded upstream
Priority:
bug
Assignee:
-
% Done:

0%


Description

Example executing ipython at the CLI results in:

Traceback (most recent call last):
  File "/usr/bin/ipython", line 5, in <module>
    from IPython import start_ipython
ModuleNotFoundError: No module named 'IPython'

My i686 machine is fully up to date. I discovered this after my workaround to this issue reported in the forum.

History

#1

Updated by doolio 4 months ago

I believe the issue is the following described in the Arch wiki (I could not find an equivalent page in the Parabola wiki).

#2

Updated by bill-auger 4 months ago

  • Status changed from unconfirmed to forwarded upstream
  • Subject changed from ModuleNotFoundError when attempting to execute any python dependent package to [i686/python]: ModuleNotFoundError when attempting to execute any python dependent package

python is pretty messed-up in arch32 upstream - there is probably nothing we can do about this - some python programs will be broken and some can not be packaged - all we can do is wait until they get it sorted out

#3

Updated by doolio 4 months ago

I see. That's unfortunate. Thanks for the update in any case.

#4

Updated by doolio 3 months ago

Any update on this issue? I couldn't find anything about this on the Arch32 bug tracker. Is it this issue.

#5

Updated by bill-auger 3 months ago

i do not expect all python programs to be working any time soon - the
migration has been ongoing since around april - you could try rebuilding your
own python dependencies - maybe even send patches to arch32 for the ones that
you get working

Also available in: Atom PDF