Change the exchange_declare and queue_declare auto_delete parameters to default to True.  I found that declaring a queue and binding it to an active exchange, and forgetting to delete it is a good way to get RabbitMQ to start consuming huge amounts of memory.  If you've created a queue with an automatically assigned name and didn't see what it was, you have to dig into erlang to find out what it was before you can remove it.
Change the exchange_declare and queue_declare auto_delete parameters
to default to True.  I found that declaring a queue and binding it
to an active exchange, and forgetting to delete it is a good way to
get RabbitMQ to start consuming huge amounts of memory.  If you've
created a queue with an automatically assigned name and didn't see
what it was, you have to dig into erlang to find out what it was
before you can remove it.

exchange_declare isn't as big a problem, but that's been changed too
for consistency.

This new defaults should be safer for casual experimentation - if a
user wants to keep a queue or exchange around, they should explicitly
say so.

dallasmarlow/py-amqp,dims/py-amqp,jonahbull/py-amqp,dims/py-amqp,jonahbull/py-amqp,dallasmarlow/py-amqp,yetone/py-amqp,newvem/py-amqplib,yetone/py-amqp,smurfix/aio-py-amqp,smurfix/aio-py-amqp