Message 170629 - Python tracker

Message170629

Author	pitrou
Recipients	amaury.forgeotdarc, jcea, pitrou, sbt, skrah
Date	2012-09-17.23:14:26
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1347923687.67.0.596836727774.issue15903@psf.upfronthosting.co.za>
In-reply-to

Content
> The bytes object cannot "leak" so, as you say, checking that refcount > is pointless. But the view might "leak", and since it does not own a > reference to the base object we have a problem: we can't deallocate the > bytes object for fear of breaking the view. Indeed, that's a problem (but your patch does deallocate the bytes object). It's quite fishy, I'm not sure how to solve the issue cleanly. Stefan, do you have an idea?

Content

> The bytes object cannot "leak" so, as you say, checking that refcount
> is pointless.  But the view might "leak", and since it does not own a
> reference to the base object we have a problem: we can't deallocate the 
> bytes object for fear of breaking the view.

Indeed, that's a problem (but your patch does deallocate the bytes object).
It's quite fishy, I'm not sure how to solve the issue cleanly. Stefan, do you have an idea?

History
Date	User	Action	Args
2012-09-17 23:14:47	pitrou	set	recipients: + pitrou, jcea, amaury.forgeotdarc, skrah, sbt
2012-09-17 23:14:47	pitrou	set	messageid: <1347923687.67.0.596836727774.issue15903@psf.upfronthosting.co.za>
2012-09-17 23:14:26	pitrou	link	issue15903 messages
2012-09-17 23:14:26	pitrou	create