<div>
<div>
<span>Hi all,</span></div><div><br></div><div>Unfortunately 0.9.4 is a fairly buggy release. It may not be related to queue_delete.</div><div><br></div><div>I'll take a look and get back to you. 0.9.5 is soon to be released, just have documentation changes to finish.</div><div><br></div><div>Regards,</div><div><br></div><div>Gavin </div><div>
<span></span>
<p style="color: #a0a0a0;">On Thursday, March 17, 2011 at 7:34 AM, curlup wrote:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div>subscribe on this.<br>could you please post here a solution if you`ll find it?<br>i`m interested but right now i have no time to take a look.<br><br>On Mar 14, 9:41 pm, vorad <vorad.1...@<a href="http://gmail.com">gmail.com</a>> wrote:<br><blockquote type="cite"><div>Hi guys,<br><br>I am offering a web service to a rabbitmq server through Tornado and I<br>am using the new pika code base (v0.9.4)<br>One of the issues or things that I don't quite grasp is how I can<br>catch errors when using queue_delete. If I am trying to delete a non-<br>existent queue, rabbitmq will raise an amqperror that I can see in my<br>logs, but it seems I miss that when using queue_delete.<br><br>How can I catch that and implement the appropriate business logic?<br><br>Thanks and sorry if I am a little bit off-topic with this one.<br></div></blockquote></div></div></span>
</blockquote>
<div>
<br>
</div>
</div>
</div>