drop 3.5 support (for now)

not testable due to async fixture

Author: smurfix

.travis.yml

@@ -1,8 +1,5 @@
 language: python
 python:
-  - 3.5.0
-  - 3.5.2
-  - 3.5-dev
   - 3.6
   - 3.6-dev
   - 3.7-dev
@@ -18,9 +15,6 @@ matrix:
     # - os: linux
     #   language: generic
     #   env: USE_PYPY_NIGHTLY=1
-    - os: osx
-      language: generic
-      env: MACPYTHON=3.5.4
     - os: osx
       language: generic
       env: MACPYTHON=3.6.3

README.rst

@@ -23,17 +23,19 @@
  trio-asyncio
 ==============
 
-``trio-asyncio`` is a re-implementation of the ``asyncio`` mainloop on top of
+**Trio-Asyncio** is a re-implementation of the ``asyncio`` mainloop on top of
 Trio.
 
+Trio-Asyncio requires Python 3.6 or 3.7. It might work on Python 3.5.
+
 +++++++++++
  Rationale
 +++++++++++
 
 Trio has native concepts of tasks and task cancellation. Asyncio is based
 on callbacks and chaining Futures, albeit with nicer syntax, which make
 handling of failures and timeouts fundamentally less reliable, esp. in
-larger programs. Thus, you *really* want to use trio in your project.
+larger programs. Thus, you *really* want to base your async project on Trio.
 
 On the other hand, there are quite a few asyncio-enhanced libraries. You
 *really* don't want to re-invent any wheels in your project.