semvec/pypi-packages huggingface dataset:
lockchain 0.0.2
Async-based context manager that enforces FIFO processing
License: MIT
Keywords: asyncio

.. image:: https://travis-ci.org/jbn/lockchain.svg?branch=master
    :target: https://travis-ci.org/jbn/lockchain
.. image:: https://ci.appveyor.com/api/projects/status/9k78nhy88v51fd69?svg=true
    :target: https://ci.appveyor.com/project/jbn/brittle-wit/branch/master
.. image:: https://coveralls.io/repos/github/jbn/lockchain/badge.svg?branch=master
    :target: https://coveralls.io/github/jbn/lockchain?branch=master 
.. image:: https://img.shields.io/pypi/dm/lockchain.svg
    :target: https://pypi.python.org/pypi/lockchain
.. image:: https://img.shields.io/pypi/v/lockchain.svg
    :target: https://pypi.python.org/pypi/lockchain
.. image:: https://img.shields.io/badge/license-MIT-blue.svg
    :target: https://raw.githubusercontent.com/jbn/lockchain/master/LICENSE
.. image:: https://img.shields.io/pypi/pyversions/lockchain.svg
    :target: https://pypi.python.org/pypi/lockchain


======================
What is ``lockchain``?
======================

A ``LockChain`` allows you to create a chain of critical regions, executed 
sequentially. The underlying Lock from asyncio would actually enforce this
with a dequeue, so this library is mostly unnecessary. Had I read the code
first, I would have either not needed this or found a different solution.
Until I actually think about it though, it's still here. 

It's still useful for limiting access to some set of resources in
a namespace. If no coroutine is blocking for some resource, it's you may
get to close that resource (or reset a rate limit.)
greyupnp 0.3
Not **all** the Python UPnP tools you could ever want. But some.
License: MIT
Requires Python: >=2.7
Keywords: upnp,ssdp

.. _repository: https://github.com/the-allanc/greyupnp/
.. _documentation: https://greyupnp.readthedocs.io/en/stable/
.. _pypi: https://pypi.python.org/pypi/greyupnp
.. _coveralls: https://coveralls.io/github/the-allanc/greyupnp
.. _license: https://github.com/the-allanc/greyupnp/master/LICENSE.txt
.. _travis: https://travis-ci.org/the-allanc/greyupnp
.. _codeclimate: https://codeclimate.com/github/the-allanc/greyupnp

.. |Build Status| image:: https://img.shields.io/travis/the-allanc/greyupnp.svg?colorB=9f9f9f
    :target: travis_
    :alt: Build Status
.. |Coverage| image:: https://img.shields.io/coveralls/the-allanc/greyupnp.svg?colorB=9f9f9f
    :target: coveralls_
    :alt: Coverage
.. |Docs| image:: https://img.shields.io/badge/docs-stable-lightgrey.svg
    :target: documentation_
    :alt: Docs
.. |Release Version| image:: https://img.shields.io/pypi/pyversions/greyupnp.svg?colorB=9f9f9f
    :target: pypi_
    :alt: Release Version
.. |Python Version| image:: https://img.shields.io/pypi/v/greyupnp.svg?colorB=9f9f9f
    :target: pypi_
    :alt: Python Version
.. |License| image:: https://img.shields.io/pypi/l/greyupnp.svg?colorB=9f9f9f
    :target: license_
    :alt: License
.. |Code Climate| image:: https://img.shields.io/codeclimate/issues/github/the-allanc/greyupnp.svg?colorB=9f9f9f
    :target: codeclimate_
    :alt: Code Climate

|Docs| |Release Version| |Python Version| |License| |Build Status| |Coverage| |Code Climate|

.. all-content-above-will-be-included-in-sphinx-docs

You can browse the source code and file bug reports at the project repository_. Full documentation can be found `here`__.

__ documentation_