hbisect.py: don't rely on __del__ to write the current state. This is yet another page of the "Thou shalt not do too much inside __del__ methods" book, in the "demandload and __del__ don't go well together" chapter. The bisect extension is broken in 0.9.1: $ hg bisect init $ hg bisect bad Fatal Python error: Interpreter not initialized (version mismatch?) Aborted (yes, I tripled checked my instalation to make sure the problem is not there) It's been broken since revision fe1689273f84 moved the import of the binascii module into a demandload. (In details: the first time that "hg bisect bad" (or good) is called, there are still no revisions saved in .hg/bisect/*, so bisect.__init__ doesn't call hg.bin on anything. So, when we reach __del__, the binascii module still hasn't been imported and we get that "nice" message above.)

     1

#!/usr/bin/env python

     2

import sys, os

     3

from mercurial import hg

     4

     5

f = sys.argv[1]

     6

     7

r1 = hg.revlog(open, f + ".i", f + ".d")

     8

r2 = hg.revlog(open, f + ".i2", f + ".d2")

     9

    10

tr = hg.transaction(open, "journal")

    11

    12

for i in xrange(r1.count()):

    13

    n = r1.node(i)

    14

    p1, p2 = r1.parents(n)

    15

    l = r1.linkrev(n)

    16

    t = r1.revision(n)

    17

    n2 = r2.addrevision(t, tr, l, p1, p2)

    18

tr.close()

    19

    20

os.rename(f + ".i", f + ".i.old")

    21

os.rename(f + ".d", f + ".d.old")

    22

os.rename(f + ".i2", f + ".i")

    23

os.rename(f + ".d2", f + ".d")