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 casevh
Recipients belopolsky, casevh, georg.brandl, jimjjewett, ked-tao, loewis, mark.dickinson, pitrou, rhettinger, skip.montanaro, tim.peters
Date 2010-10-17.19:35:35
SpamBayes Score 1.8571717e-07
Marked as misclassified No
Message-id <1287344137.07.0.41947840388.issue9778@psf.upfronthosting.co.za>
In-reply-to
Content
I'm the maintainer of a third-party library (gmpy) that would be impacted by this and I'm definately in favor of this change. With ever increasing amounts of memory becoming standard in computers, more users will encounter performance issues with large dictionaries. I see 3.2 as the version of Python 3.x that gains wide-spread use. Regardless of the timing of a stable ABI, it's popularity will make it more difficult change the hash size in the future.
History
Date User Action Args
2010-10-17 19:35:37casevhsetrecipients: + casevh, tim.peters, loewis, skip.montanaro, georg.brandl, rhettinger, jimjjewett, mark.dickinson, belopolsky, pitrou, ked-tao
2010-10-17 19:35:37casevhsetmessageid: <1287344137.07.0.41947840388.issue9778@psf.upfronthosting.co.za>
2010-10-17 19:35:35casevhlinkissue9778 messages
2010-10-17 19:35:35casevhcreate