Package: python3.4
Version: 3.4.3-4
Followup-For: Bug #783787
This seems to break Python 3 and with it all Python 3-dependent scripts on
affected machines due to `_sysconfigdata_m.py` not existing in the import path
when called from `/usr/lib/python3.4/_sysconfigdata.py`. The module exists in
the `/usr/lib/python3.4/plat-i386-linux-gnu` directory, though.
A quick workaround in a single command for those finding this bug report who
just want to get it working immediately could be to run
sudo ln -sr /usr/lib/python3.4/plat-i386-linux-gnu/_sysconfigdata_m.py \
/usr/lib/python3.4/
(verified to work on my local system) while remembering to revert the manual
workaround as soon as a "proper" fix rolls in.
-- System Information:
Debian Release: 8.0
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages python3.4 depends on:
ii libpython3.4-stdlib 3.4.3-4
ii mime-support 3.58
ii python3.4-minimal 3.4.3-4
python3.4 recommends no packages.
Versions of packages python3.4 suggests:
ii binutils 2.25-7
pn python3.4-doc <none>
ii python3.4-venv 3.4.3-4
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
