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 josh.r
Recipients Devin Jeanpierre, josh.r, rhettinger
Date 2015-01-08.22:49:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Note: index returns without the caller having a chance to execute code that would change the sequence length directly. But other threads could change it, as could a custom __eq__ on an object stored in the sequence (or a poorly implemented __getitem__ or __len__ on the sequence itself, but that's getting even more pathological). Thread consistency is the code's responsibility though (we just need to make sure we behave the best we can, and hope they use locks correctly), and the odds of equality of __getitem__ altering the sequence are much lower than the odds of someone iterating the sequence and changing it as they go (which is what __iter__'s implementation allows, responding with potentially incomplete results since items might be skipped due to the mutation), but keeping the sequence in a consistent state.
Date User Action Args
2015-01-08 22:49:41josh.rsetrecipients: + josh.r, rhettinger, Devin Jeanpierre
2015-01-08 22:49:41josh.rsetmessageid: <>
2015-01-08 22:49:41josh.rlinkissue23086 messages
2015-01-08 22:49:41josh.rcreate