On Tue, Dec 30, 2014 at 4:28 AM, Peter Otten <__pete...@web.de> wrote: > Maybe the interpreter itself is corrupted? Google suggests that debsums may > be the tool to find out.
That's part of what I'm trying to track down, but why it should have changed in the past few days is beyond me. There's no way that rebuilding Python 3.5 should break Python 2.7 on the same system, right? I haven't installed any Debian updates this week. Just tried debsums, and it isn't complaining about any corruption or damage. ChrisA -- https://mail.python.org/mailman/listinfo/python-list
