From 77058df3bdf32e692c9415172e0a59c6f7ac7d80 Mon Sep 17 00:00:00 2001
From: Piotr Maslanka <piotr.maslanka@henrietta.com.pl>
Date: Wed, 11 Jan 2017 00:19:51 +0100
Subject: [PATCH] v0.81

---
 README.md | 8 ++++++++
 setup.py  | 3 ++-
 2 files changed, 10 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index d13b002..fd94e21 100644
--- a/README.md
+++ b/README.md
@@ -16,12 +16,20 @@ and there are memoryviews **_everywhere_**.
 
 This is borderline absurd.
 
+CoolAMQP is not a direct AMQP client - it also handles reconnections, transactional sending,
+and so on, mostly via Futures. This means it has a certain opinion on how to 
+handle AMQP, but you can feel the spirit of AMQP underneath.
+
 
 The project is actively maintained and used in a commercial project. Tests can run
 either on Vagrant (Vagrantfile attached) or Travis CI, and run against RabbitMQ.
 
+CoolAMQP won't touch your messages. It's your bag of bytes, and your properties.
+
 Enjoy!
 
+_Watch out for memoryviews!_
+
 
 ## Notes
 Assertions are sprinkled throughout the code. You may wish to run with optimizations enabled
diff --git a/setup.py b/setup.py
index 49dda78..fab0acb 100644
--- a/setup.py
+++ b/setup.py
@@ -22,7 +22,8 @@ setup(name=u'CoolAMQP',
           'coolamqp.framing.compilation',
       ],
       license=u'MIT License',
-      long_description=u'''AMQP client, but with dynamic class generation and memoryviews FOR THE GODSPEED.
+      long_description=u'''Pure Python AMQP client, but with dynamic class generation and memoryviews FOR THE GODSPEED.
+
 Also, handles your reconnects and transactionality THE RIGHT WAY''',
       requires=['amqp', 'six', 'monotonic'],
       tests_require=["nose"],
-- 
GitLab