This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author jojo
Recipients jojo, ned.deily, yaro-yaro
Date 2016-05-23.22:15:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1464041700.29.0.920105318117.issue26971@psf.upfronthosting.co.za>
In-reply-to
Content
I can confirm this issue. I did run it on Linux SuSE 13.1 (64 Bit). Unlike other components, which are installed in `lib/`, `lib-dynload` is installed in `lib64/python3.5/`. But `sys.path` still points to `lib/python3.5/lib-dynload`. It did run in on :

mkdir build
cd build
../configure --prefix="${HOME}/.opt"
nice -n 19 make -j 6
make install
History
Date User Action Args
2016-05-23 22:15:00jojosetrecipients: + jojo, ned.deily, yaro-yaro
2016-05-23 22:15:00jojosetmessageid: <1464041700.29.0.920105318117.issue26971@psf.upfronthosting.co.za>
2016-05-23 22:15:00jojolinkissue26971 messages
2016-05-23 22:15:00jojocreate