Package list aiocoap / multiarch-fixes/main

Tree @multiarch-fixes/main (Download .tar.gz)

aiocoap -- The Python CoAP library

The aiocoap package is a Python implementation of CoAP, the Constrained
Application Protocol (`RFC 7252`_, more info at

It uses the Python 3's asynchronous I/O to facilitate concurrent operations
while maintaining a simple to use interface and not depending on anything
outside the standard library.

aiocoap is originally based on txThings_. If you want to use CoAP in your
existing twisted application, or can not migrate to Python 3 yet, that is
probably more useful to you than aiocoap.

.. _`RFC 7252`:
.. _txThings:


For how to use the aiocoap library, have a look at the guidedtour_, or at
the examples_ and tools_ provided. All the details are in the
`aiocoap module`_ documentation.

All examples can be run directly from a source code copy. If you prefer to
install it, the usual Python mechanisms apply (see installation_).

Features / Standards

This library supports the following standards in full or partially:

* RFC7252_ (CoAP): missing are a caching and cross proxy implementation, proper
  multicast (support is incomplete), and DTLS.
* RFC7641_ (Observe): Reordering, re-registration, and active cancellation are
* RFC7959_ (Blockwise): Multicast exceptions missing.
* draft-ietf-core-etch-04_: Only registry entries added, but that should be all
  that's neede on the library side.

If something described by one of the standards but not implemented, it is
considered a bug; please file at the `github issue tracker`_. (If it's not on
the list or in the excluded items, file a wishlist item at the same location).

.. _RFC7252:
.. _RFC7641:
.. _RFC7959:
.. _draft-ietf-core-etch-04:


The core aiocoap functionality works out of the box with Python_ 3.4; with the
additional asyncio_ module, it works with version 3.3 as well. The
examples_ require Python 3.5 or newer.

When application/link-format typed resources (`RFC 6690`_) are supposed to be
used, the `link_header`_ module is required as well. When the respective code
paths are used without the module, an ``ImportError`` will be raised, or a
5.00 status code will be returned. Python modules that implement servers or
use discovery with aiocoap should declare a dependency on
``'aiocoap[linkheader]'`` instead of ``'aiocoap'``.

.. _Python:
.. _asyncio:
.. _`RFC 6690`:
.. _`link_header`:


aiocoap tries to stay close to PEP8_ recommendations and general best practice,
and should thus be easy to contribute to. Unit tests are implemented in the
``./tests/`` directory and easiest run using ``./ test``; complete test
coverage is aimed for, but not yet complete (and might never be, as the error
handling for pathological network partners is hard to trigger with a library
designed not to misbehave).

Documentation is built using sphinx_ with ``./ build_sphinx``; hacks
used there are described in ``./doc/README.doc``.

Bugs (ranging from "design goal" and "wishlist" to typos) are currently tracked
in the `github issue tracker`_.

.. _PEP8:
.. _sphinx:
.. _`github issue tracker`:

Relevant URLs


  This is where the latest source code can be found, and bugs can be reported.
  Generally, this serves as the project web site.


  Online documentation built from the sources.


  Further general information on CoAP, the standard documents involved, and
  other implementations and tools available.


aiocoap is published under the MIT License, see LICENSE_ for details.

When using aiocoap for a publication, please cite it according to the output of
``./ cite [--bibtex]``.

Copyright (c) 2012-2014 Maciej Wasilak <>,
              2013-2014 Christian Amsüss <>

.. _guidedtour:
.. _examples:
.. _tools:
.. _installation:
.. _`aiocoap module`: