semvec/pypi-packages huggingface dataset:
gbdx-task-template 0.1.5
GBDX Task Template
License: MIT

==================
gbdx-task-template
==================

.. image:: https://circleci.com/gh/michaelconnor00/gbdx-task-template/tree/master.svg?style=shield
    :target: https://circleci.com/gh/michaelconnor00/gbdx-task-template/tree/master

.. image:: https://badge.fury.io/py/gbdx-task-template.svg
    :target: https://badge.fury.io/py/gbdx-task-template

A super class template for custom tasks to be run using gbdx-cloud-harness, see https://github.com/TDG-Platform/cloud-harness.

Development
-----------

**Contributing**

Please contribute! Please make pull requests directly to master. Before making a pull request, please:

* Ensure that all new functionality is covered by unit tests.
* Verify that all unit tests are passing.
* Ensure that all functionality is properly documented.t
* Ensure that all functions/classes have proper docstrings so sphinx can autogenerate documentation.
* Fix all versions in setup.py (and requirements.txt)

**Run Tests**

Tests use `pytest`_ framework

.. _pytest: http://pytest.org/latest/contents.html

::

  py.test [...]
  python -m pytest [...]


**Create a new version**

To create a new version::

    bumpversion ( major | minor | patch )
    git push --tags

Don't forget to update the changelog
ua2.patch 2.0.0
UA2WEB Django patch system
License: MIT
Keywords: django migration utility

What this package does?
=======================

This package provides an easy half-manual and controlled way to define and run SQL, Python and Shell script for your project.

Supported backends
==================

-   MySQL
-   PostgreSQL

Supported Django versions
=========================

-   Django &gt;= 1.8

Supported OS
============

-   Linux
    -   Ubuntu 14.04
    -   Ubuntu 16.04

Why to use this package if there is django-migrations and South?
================================================================

The differencies between Django migrations and ua2.patch are in purpose:

-   django-migrations primary purpose is to propogate changes you make to your models into your database
-   ua2.patch purpose is to create & maintain patches, written by big development team

This package could be used in parallel to existing django-migrations module, or it can completely replace the job done by migrations. You, as developer, decide where you should use one or another.

We are not going to replicate all migration features, the core idea of this package is to provide easy to use tool to create and maintain (SQL|Python|Shell) patches for big team of people, working in parallel on different branches.

What are benefits of using ua2.patch ?
======================================

Simple way to automate running custom patches
---------------------------------------------

It is very easy to create patches for your data.

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

Install package from pip
------------------------

First, install package via pip:

``` example
pip install ua2.patch
```

And then, add it to your Django INSTALLED<sub>APPS</sub>:

``` example
INSTALLED_APPS = [
    ...
    'ua2.patch',
]
```

Usage examples
==============

Create SQL patch
----------------

``` example
./manage.py patch next
File .../patches/00002-johnsmith-014.sql has been created
    size: 0
```

Now, you can open & edit the file. *Note*: until file size is zero, it would not be applied, but will be treated as *reserved* patch for future use.

Create Python patch
-------------------

``` example
./manage.py patch next -e py
File .../patches/00002-johnsmith-022.py has been created
    size: 0
```

*Note:* patch body should have function main() which returns True. If you don't return True, the system will run the patch and exit on this place, preventing other scripts to run.

Create Shell patch
------------------

``` example
./manage.py patch next -e sh
File .../patches/00003-johnsmith-022.sh has been created
    size: 0
```
Flask-Celery-py3 0.2.4
Celery 3.0+ integration for Flask (Python 3 version)
License: MIT

=============================
Flask Celery 3.0+ Integration
=============================
.. image:: https://img.shields.io/pypi/v/Flask-Celery-py3.svg
    :target: https://pypi.python.org/pypi/Flask-Celery-py3/
.. image:: https://img.shields.io/pypi/dm/Flask-Celery-py3.svg
    :target: https://pypi.python.org/pypi/Flask-Celery-py3/
.. image:: https://img.shields.io/pypi/l/Flask-Celery-py3.svg
    :target: https://pypi.python.org/pypi/Flask-Celery-py3
.. image:: https://img.shields.io/pypi/pyversions/Flask-Celery-py3.svg
    :target: https://pypi.python.org/pypi/Flask-Celery-py3/
.. image:: https://img.shields.io/pypi/status/Flask-Celery-py3.svg
    :target: https://pypi.python.org/pypi/Flask-Celery-py3/

Celery: http://celeryproject.org

Using Flask-Celery
==================

You can easily add Celery to your flask application like this:

``app.py``::

    from flask_celery import Celery

    celery = Celery()

    def create_app():
        app = Flask(__name__)

        celery.init_app(app)

        return app

    @celery.task
    def add(x, y):
        return x + y

To start the worker you can then launch the ``celery worker`` command
by pointing to your ``celery`` app instance::

    $ celery -A app:celery worker -l info

If your flask application has complex condition, you can refer to the example https://github.com/taogeT/flask-celery .