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 terry.reedy
Recipients daniel.urban, dmtr, eric.araujo, ezio.melotti, mark.dickinson, pitrou, rhettinger, terry.reedy
Date 2010-08-08.20:27:01
SpamBayes Score 6.693512e-05
Marked as misclassified No
Message-id <1281299223.24.0.824204946783.issue9520@psf.upfronthosting.co.za>
In-reply-to
Content
A decade ago, 8gig memory was rare, now it is almost standard for high-end consumer machines. People are now doing bigger computations and stressing the implementation more. So it is plausible that we need to either tweak the core class implementations or (non-exclusively) add specialize structures optimized for certain tasks.

However, please to not throw the word 'bug' around lightly. When inappropriate, it only gets in the way. The language standard intentionally omits performance guarantees, especially when running on fragmented finite memory with multiple cache levels and possible OS limitations.
History
Date User Action Args
2010-08-08 20:27:03terry.reedysetrecipients: + terry.reedy, rhettinger, mark.dickinson, pitrou, ezio.melotti, eric.araujo, daniel.urban, dmtr
2010-08-08 20:27:03terry.reedysetmessageid: <1281299223.24.0.824204946783.issue9520@psf.upfronthosting.co.za>
2010-08-08 20:27:01terry.reedylinkissue9520 messages
2010-08-08 20:27:01terry.reedycreate