semvec/pypi-packages huggingface dataset:
flask-apidoc 1.0.0
Adds ApiDoc support to Flask
License: MIT
Keywords: flask,apidoc,doc,documentation,rest,restful

=================================
Flask ApiDoc
=================================
Flask ApiDoc is a Flask extension which adds support for the ApiDoc_.

|Version|

Features
===============
- Flask-Script command to generate the apidoc's files, by default they are generated into static/docs
- Hosts the apidoc's files, by default they are hosted in http://localhost:5000/docs

Documentation
===============
Soon... take a look at the example_ to see how it works.

Installation
===============
You can install flask-apidoc via Python Package Index (PyPI_),::

    $ pip install flask-apidoc

Feedback
===============
Please use the Issues_ for feature requests and troubleshooting usage.

.. |Version| image:: https://badge.fury.io/py/flask-apidoc.svg
   :target: http://badge.fury.io/py/flask-apidoc

.. _ApiDoc: http://www.apidocjs.com

.. _example: https://github.com/viniciuschiele/flask-apidoc/tree/master/example

.. _PyPi: https://pypi.python.org/pypi/flask-apidoc

.. _Issues: https://github.com/viniciuschiele/flask-apidoc/issues
datetimeutc 0.1.1
Because why are we dealing with timezones?
License: MIT
Keywords: datetime,timezone,utc

datetimeutc

A Python datetime wrapper so we can forget about timezones

A lightweight datetime utility library which wraps around the standard `datetime` module, with features from dateutil and pytz.

Its purpose is to minimize the effort to convert datetime to/from UTC, a task I found myself doing too often while scaling web services and apps internationally.

This wrapper is designed under these datetime philosophy:

1. datetime should always be timezone aware
2. datetime should always be handled and stored in UTC time
3. datetime should always default to UTC time
4. datetime should not contain server local time
5. timezone conversions should be done on client side

Install

    $ pip install datetimeutc

Usage

The library provides thinly wrappers of datetime classes, e.g. datetime, date, and time.

Instances of these class are created with timezone awareness in UTC time. Users can also pass in `None` or other timezone, which the library will automatically converts into UTC time.

>>> from datetimeutc import Datetime, Date, Time
>>> import pytz
>>> d = Datetime(2016, 3, 21, 9, 20, 40)
Datetime(2016, 3, 21, 9, 20, 40, tzinfo=<UTC>)
>>> Datetime(2016, 3, 21, 9, 20, 40, tzinfo=pytz.timezone('US/Eastern'))
Datetime(2016, 3, 21, 14, 16, 40, tzinfo=<UTC>)

Functions of datetime are all supported.

>>> from datetimeutc import Datetime, Date, Time
>>> Datetime.now()
Datetime(2016, 3, 21, 9, 20, 40, 816025, tzinfo=<UTC>)
>>> Datetime.now().dst()      
datetime.timedelta(0)
>>> Datetime.now().timetuple()
time.struct_time(tm_year=2016, tm_mon=3, tm_mday=21, tm_hour=9, tm_min=7, tm_sec=47, tm_wday=0, tm_yday=81, tm_isdst=0)
>>> Datetime.now().toordinal()
736044
>>> Datetime.now().isoweekday()
1
>>> Datetime.now().isoformat()
'2016-03-21T09:08:17.488494+00:00'
>>> Datetime.strptime('2016-03-21','%Y-%m-%d')
Datetime(2016, 3, 21, 0, 0, tzinfo=<UTC>)
>>> datetimeutc.Datetime(2016, 3, 21, 9, 20, 40).astimezone(pytz.timezone('US/Eastern'))
datetime.datetime(2016, 3, 21, 5, 20, 40, tzinfo=<DstTzInfo 'US/Eastern' EDT-1 day, 20:00:00 DST>)

Utilities

Other datetime functions are available for common tasks, e.g. converting to/from javascript timestamp

>>> import datetimeutc, datetime
>>> datetimeutc.to_utc(datetime.datetime.now())
datetime.datetime(2016, 3, 21, 9, 31, 8, 455166, tzinfo=<UTC>)
>>> d = datetimeutc.Datetime(2016, 3, 21, 9, 20, 40)
>>> d
Datetime(2016, 3, 21, 9, 20, 40, tzinfo=<UTC>)
>>> d.timestamp
1458552040
>>> d.jstimestamp 
1458552040000.0
>>> datetimeutc.Datetime.from_jstimestamp(d.jstimestamp)
Datetime(2016, 3, 21, 9, 20, 40, tzinfo=<UTC>)
simple-workflow 0.1.60
Amazon simple workflow service wrapper for python
License: MIT
Keywords: amazon simple wokflow swf python

======================
Python Simple Workflow
======================

.. image:: https://travis-ci.org/botify-labs/python-simple-workflow.png?branch=develop

python-simple-workflow is a wrapper for `Amazon Simple Workflow <http://aws.amazon.com/en/swf/>`_ service.
It aims to provide some abstractions over the webservice concepts through `Boto <https://boto.readthedocs.org/en/latest/ref/swf.html>`_ library Swf api implementation.

It aims to provide:

* **Modelisation**: Swf entities and concepts are to be manipulated through `Models <http://test.com>`_ and `QuerySets <http://test.com>`_ (any ressemblance with the `Django <http://test.com>`_ api would not be a coincidence).
* **High-level Events, History**: A higher level of abstractions over Swf *events* and *history*. Events are implemented as stateful objects aware of their own state and possible transitions. History enhance the events flow description, and can be compiled to check it's integrity and the activities statuses transitions.
* **Decisions**: Stateful abstractions above the Swf decision making system.
* **Actors**: Swf actors base implementation such as a `Decider <http://test.com>`_ or an activity task processor `Worker <http://test.com>`_ from which the user can easily inherit to implement it's own decision/processing model.

It provides querysets and model objects over commonly used concepts: domains, workflow types, activity types, and so on.

It is under MIT license, and any ideas, features requests, patches, pull requests to improve it are of course welcome.

Installation
============

.. code-block:: shell

    pip install simple-workflow


Usage and all the rest
======================

Please, refer to `Documentation <http://python-simple-workflow.readthedocs.org>`_