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 josh.r, rhettinger
Date 2015-03-31.10:39:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1427798347.06.0.889412710172.issue23793@psf.upfronthosting.co.za>
In-reply-to
Content
I agree that popping old inputs is the normal way. What I'm trying to say is that it doesn't feel like "old" or "inputs" when you multiply. In that case (and maybe this is just me), it feels like a "reasonable" outcome could be to get an outcome similar to multiplying a list and then slicing the result to maxlen. I don't think it *should* do that, but either behavior feels weird, solely because sequence multiplication has never been applied to a bounded sequence before (to my knowledge), so the expectations aren't set.

You end up with weird behaviors like len(seq) * 3 != len(seq * 3), which is a normal and expected outcome with every other sequence. If you know you're dealing with a bounded deque, it's less unexpected, but this is trying to make a deque a drop-in replacement for any other sequence when it doesn't behave like one.
History
Date User Action Args
2015-03-31 10:39:07josh.rsetrecipients: + josh.r, rhettinger
2015-03-31 10:39:07josh.rsetmessageid: <1427798347.06.0.889412710172.issue23793@psf.upfronthosting.co.za>
2015-03-31 10:39:07josh.rlinkissue23793 messages
2015-03-31 10:39:06josh.rcreate