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 pitrou
Recipients belopolsky, casevh, georg.brandl, jimjjewett, ked-tao, loewis, mark.dickinson, pitrou, rhettinger, skip.montanaro, tim.peters
Date 2010-10-15.19:12:26
SpamBayes Score 6.0238284e-07
Marked as misclassified No
Message-id <1287169943.3422.7.camel@localhost.localdomain>
In-reply-to <>
> 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.
Date User Action Args
2010-10-15 19:12:28pitrousetrecipients: + pitrou, tim.peters, loewis, skip.montanaro, georg.brandl, rhettinger, jimjjewett, mark.dickinson, belopolsky, casevh, ked-tao
2010-10-15 19:12:26pitroulinkissue9778 messages
2010-10-15 19:12:26pitroucreate