diff --git a/boltons/queueutils.py b/boltons/queueutils.py
index 59d478a..e061e16 100644
--- a/boltons/queueutils.py
+++ b/boltons/queueutils.py
@@ -68,12 +68,12 @@ class BasePriorityQueue(object):
 
     Args:
         priority_key (callable): A function that takes *priority* as
-            passed in by :meth:`add` and returns an integer
+            passed in by :meth:`add` and returns a real number
             representing the effective priority.
 
     """
     # negating priority means larger numbers = higher priority
-    _default_priority_key = staticmethod(lambda p: -int(p or 0))
+    _default_priority_key = staticmethod(lambda p: -float(p or 0))
     _backend_type = list
 
     def __init__(self, **kw):

diff --git a/tests/test_queueutils.py b/tests/test_queueutils.py
index 8d83671..710a0cd 100644
--- a/tests/test_queueutils.py
+++ b/tests/test_queueutils.py
@@ -5,14 +5,36 @@ from boltons.queueutils import SortedPriorityQueue, HeapPriorityQueue
 
 def _test_priority_queue(queue_type):
     pq = queue_type()
-    func = lambda x: x
-    pq.add(func)
-    pq.remove(func)
-    pq.add(func)
-    pq.add(func)
+    item1 = 'a'
+    item2 = 'b'
+    item3 = 'c'
+    pq.add(item1)
+    pq.remove(item1)
+
+    # integer priorities
+    pq.add(item1, 2)
+    pq.add(item2, 9)
+    pq.add(item3, 7)
+    assert len(pq) == 3
+    assert item2 == pq.pop()
+    assert len(pq) == 2
+    assert item3 == pq.pop()
     assert len(pq) == 1
-    assert func == pq.pop()
+    assert item1 == pq.pop()
     assert len(pq) == 0
+
+    # float priorities
+    pq.add(item1, 0.2)
+    pq.add(item2, 0.9)
+    pq.add(item3, 0.7)
+    assert len(pq) == 3
+    assert item2 == pq.pop()
+    assert len(pq) == 2
+    assert item3 == pq.pop()
+    assert len(pq) == 1
+    assert item1 == pq.pop()
+    assert len(pq) == 0
+
     try:
         pq.pop()
     except IndexError:

Priority queue does not support float priorities
Through a lot of painful debugging in a larger codebase, I found that both of boltons priority queue implementations treat a float priority `p` as if it were `int(p)`.

```
In [1]: from boltons.queueutils import PriorityQueue

In [2]: items = [('a', 0.8), ('b', 0.9), ('c', 0.6), ('d', 1.8), ('e', 1.9), ('f', 1.6)]

In [3]: q = PriorityQueue()

In [4]: for i, p in items: q.add(i, p)

In [5]: for i in range(6): print(q.pop())
d
e
f
a
b
c
```

See the behavior that personally I would expect in this situation, exhibited by a depq package for double-ended priority queues:
```
In [6]: from depq import DEPQ

In [7]: q = DEPQ(items)

In [8]: for i in range(6): print(q.popfirst())
('e', 1.9)
('d', 1.8)
('f', 1.6)
('b', 0.9)
('a', 0.8)
('c', 0.6)
```

I believe the current behavior should be explicitly documented. It's not clear that the priorities would be treated as if they were floored neither from the current docs nor from a brief look at the source.
tests/test_queueutils.py::test_heap_queue tests/test_queueutils.py::test_sorted_queue