> Given the range of people advocating for this change, this looks to me
> like it should be a release blocker for 3.2.  Raymond's comment about
> performance seems especially important, and since the world seems to
> be moving toward 64-bit operating systems (certainly should happen in
> a big way during the lifetime of Python 3) it seems worthwhile to hold
> up further 3.2 releases until this is solved.

I think this is a bit exagerated. The performance issues will only
appear if you have huge dicts and sets.
The issue Raymond raised is the potential impossibility of making the
change /after/ we settle on a stable ABI. The question is whether the
ABI will be enforced starting from 3.2, or from a later date.