semvec/pypi-packages huggingface dataset:
owntwin 0.2.0
User-driven digital twin framework.
License: MIT
Requires Python: >=3.9,<4.0

# OwnTwin CLI

[![PyPI](https://img.shields.io/pypi/v/owntwin.svg)](https://pypi.python.org/pypi/owntwin/)
[![PyPI - Downloads](https://img.shields.io/pypi/dm/owntwin.svg)](https://pypistats.org/packages/owntwin)

OwnTwin CLI is a toolchain for [OwnTwin](https://github.com/owntwin/owntwin), a user-driven digital twin framework.

## Installation

```
pip install owntwin
```

_Note for Windows users:_ [Fiona](https://github.com/Toblerity/Fiona#installation) is required to be preinstalled.

## Usage

See the [documentation](https://beta.owntwin.com/docs/getting-started) for details.

```
owntwin init
owntwin add-terrain
owntwin add [module names...]
owntwin export
owntwin view
```
WSME 0.12.1
Simplify the writing of REST APIs, and extend them with additional protocols.
License: MIT
Requires Python: >=3.8

Web Services Made Easy
======================

Introduction
------------

Web Services Made Easy (WSME) simplifies the writing of REST web services
by providing simple yet powerful typing, removing the need to directly
manipulate the request and the response objects.

WSME can work standalone or on top of your favorite Python web
(micro)framework, so you can use both your preferred way of routing your REST
requests and most of the features of WSME that rely on the typing system like:

- Alternate protocols, including those supporting batch-calls
- Easy documentation through a Sphinx_ extension

WSME is originally a rewrite of TGWebServices with a focus on extensibility,
framework-independence and better type handling.

How Easy?
~~~~~~~~~

Here is a standalone WSGI example::

    from wsme import WSRoot, expose

    class MyService(WSRoot):
        @expose(unicode, unicode)  # First parameter is the return type,
                                   # then the function argument types
        def hello(self, who=u'World'):
            return u"Hello {0} !".format(who)

    ws = MyService(protocols=['restjson', 'restxml'])
    application = ws.wsgiapp()

With this published at the ``/ws`` path of your application, you can access your
hello function in various protocols:

.. list-table::
    :header-rows: 1

    * - URL
      - Returns

    * - ``http://<server>/ws/hello.json?who=you``
      - ``"Hello you !"``

    * - ``http://<server>/ws/hello.xml``
      - ``<result>Hello World !</result>``

Main features
~~~~~~~~~~~~~

- Very simple API.

- Supports user-defined simple and complex types.

- Multi-protocol : REST+JSON, REST+XML and more possible.

- Extensible : easy to add more protocols or more base types.

- Framework independence : adapters are provided to easily integrate your API in
  any web framework, for example an WSGI container, Pecan_, Flask_, ...

- Very few runtime dependencies: webob, simplegeneric.

- Integration in `Sphinx`_ for making clean documentation with
  ``wsmeext.sphinxext``.

.. _Pecan: http://pecanpy.org/
.. _Flask: http://flask.pocoo.org/

Install
~~~~~~~

::

    pip install WSME

Changes
~~~~~~~

- Read the `Changelog`_

Getting Help
~~~~~~~~~~~~

- Read the `WSME Documentation`_.
- Questions about WSME should go to the `python-wsme mailinglist`_.

Contribute
~~~~~~~~~~

- Documentation: http://packages.python.org/WSME/
- Source: http://git.openstack.org/cgit/openstack/wsme
- Bugs: https://bugs.launchpad.net/wsme/+bugs
- Code review: https://review.openstack.org/#/q/project:openstack/wsme,n,z

.. _Changelog: http://packages.python.org/WSME/changes.html
.. _python-wsme mailinglist: http://groups.google.com/group/python-wsme
.. _WSME Documentation: http://packages.python.org/WSME/
.. _WSME issue tracker: https://bugs.launchpad.net/wsme/+bugs
.. _Sphinx: http://sphinx.pocoo.org/