Document context managers

Author: mark9064

README.md

@@ -36,13 +36,17 @@ Available methods in both classes are (see docstrings for more info):
 * send_command - Sends a single command to the RCON server.
 * send_commands - Sends multiple commands to the RCON server.
 
+Note that both the sync/async clients can be used as sync/async context managers respectively.
+
 The methods for sending/receiving packets are available in case you want to
 write your own packet handlers, but in most cases you will never need to touch
 these and can use send_command(s).
 
 ## Mentions
 
-Thanks to [Truman Kilen](https://github.com/trumank) for the initial code / idea.
+Thanks to:
+- [Truman Kilen](https://github.com/trumank) for the initial code / idea.
+- [De Sa Léo](https://github.com/desaleo) for contributing context manager support.
 
 ## License
 

factorio_rcon/_factorio_rcon.py

@@ -189,6 +189,7 @@ class RCONClient(RCONSharedBase):
     Extra information:
         **All methods are not thread safe**
         Use AsyncRCONClient for coroutine based concurrency.
+        This is usable as a context manager.
         If any exception is raised (all inherit from RCONBaseError) during operation,
         it is required that you reconnect to the RCON server (with .connect()).
         The server will not respond to any RCON requests if it is saving, so you should
@@ -434,6 +435,7 @@ class AsyncRCONClient(RCONSharedBase):
 
         anyio allows you to use either asyncio or trio.
         All functions in this class are async.
+        This is usable as an async context manager.
         If you want to set timeouts, use the cancellation system your existing framework
         provides or use anyio.move_on_after/fail_after.
         See https://anyio.readthedocs.io/en/latest/cancellation.html#timeouts.