On 09/01/2015 12:09 PM, David Magda wrote:
Could the new version of Python been chocking on a binary file whose
format has changed from the old version? Is it prudent to do an "arch
--wipe" when changing versions of Python?

The exception is thrown in Python's sort() method. There are no
documented changes in this method's calling sequence between Python 2.5
and 2.6, but it's quite possible there were changes in the details of
the key comparison code that are responsible.

No it is not prudent to do an "arch --wipe" when changing versions of
Python?. It is not a good idea to ever do "arch --wipe" unless it's
really necessary. See the section "NOTE ON MBOX ANOMALIES:" at

Mark Sapiro <mark@msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan

Search Discussions

Discussion Posts


Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 9 of 16 | next ›
Discussion Overview
groupmailman-users @
postedSep 1, '15 at 11:22a
activeSep 2, '15 at 8:33p



site design / logo © 2021 Grokbase