semvec/pypi-packages huggingface dataset:
tf-init-booster 1.2.0
terraform init booster
Requires Python: >=3.6

# terraform-init-booster

![GitHub last commit](https://img.shields.io/github/last-commit/hayorov/terraform-init-booster)
![PyPI](https://img.shields.io/pypi/v/tf-init-booster)
![PyPI - Downloads](https://img.shields.io/pypi/dm/tf-init-booster)
![GitHub issues](https://img.shields.io/github/issues/hayorov/terraform-init-booster)

_A Pre-terraform routine that speedups terraform modules download for bulky blueprints._

## Problem statement

- Terraform v0.12.x and older downloads module from git source for every usage (<https://github.com/hashicorp/terraform/issues/11435>). For bulky blueprints with hundreds of similar modules that make the process of `terraform init` slow.

## Installation

    pip install tf-init-booster

## Quickstart

    (blueprint folder)>tf-init-booster
    (blueprint folder)>terraform init

## Settings with environment variables

- LOGLEVEL=INFO
- GIT_PATH=/usr/bin/git

## Indications for use

- Git as module source
- Many modules with the same source

## Performance

Based on a blueprint with 580 modules, 10 of them unique.

- Pure `terraform init` - 3m08s
- Boosted + `terraform init` - 39s (2.7s + 36.5s)

## Compatibility

Designed for terraform v0.12 and v0.11

## Requrements

- Python 3.6+
- (optional) gitpython * module

\* otherwise, system git will be used
djcall 0.4.6
Leverage uWSGI spooler and cron in Django
Keywords: django uwsgi cache spooler

Requirements
============

Upgrade from v0.3 to v0.4
=========================

As of v0.4, djcall uses a PostgreSQL JSON field instead of a Picklefield for
Caller.kwargs, which means that unless you have only JSON serializable contents
in your djcall_caller.kwargs columns: the migration will fail, so will it if
you don't run PostgreSQL. Sorry, but it became too much of an annoyance not to
be able to query of Call kwargs. Anyway, a migration should take care of this
for you. It leaves the old Picklefield renamed from kwargs to old_kwargs until
next release where it will be dropped.

Install
=======

pip install djcall

Add djcall to INSTALLED_APPS and migrate.

Usage
=====

.. code-block:: python

    from djcall.models import Caller

    Caller(
        # path to python callback
        callback='djblockchain.tezos.transaction_watch',
        # JSON serializable kwargs
        kwargs=dict(
            pk=transaction.pk,
        ),
    ).spool('blockchain')  # optionnal spooler name

No decorator, no nothing,

If you have CRUDLFA+ or django.contrib.admin, you should see the jobs there,
and be able to cancel them.

Example project
===============

Setup example project::

    djcall-example collectstatic
    djcall-example migrate
    djcall-example createsuperuser

Run with runserver::

    djcall-example runserver

Or with uWSGI::

    uwsgi --env DJANGO_SETTINGS_MODULE=djcall_example.settings --env DEBUG=1 --spooler=/spooler/blockchain --spooler=/spooler/mail --spooler-processes 1 --http=:8000 --plugin=python --module=djcall_example.wsgi:application --honour-stdin --static-map /static=static

History
=======

First made a dead simple pure python generic spooler for uwsgi:
https://gist.github.com/jpic/d28333b0573c3c555fbe6e55862ecddb

The made a first implementation including CRUDLFA+ support:
https://github.com/yourlabs/django-uwsgi-spooler

This version adds:

- Cron model and support for uWSGI cron, can't add/remove them without restart,
  but can change kwargs and options online
- CRUDLA+ support is on hold waiting for what's currently in
  https://github.com/tbinetruy/CHIP because i don't want to build crud support
  here with templates because of the debt this will add, it's time to use
  components in CRUDLFA+ to make the CRUD for Cron/Background tasks awesome
parserBI 0.0.3
A python module to parse source code for retro-documentation
Requires Python: >=3.5, <4
Keywords: sample,setuptools,development

# Parser en Python

## Description
Ce repo contient le code d'un module python permettant de parser du code source pour en extraire des indicateurs.

## Installation
Depuis Git bash : 

1. Cloner le projet (master)
2. cd parser
3. pip install -r requirements.txt
4. py.test

## Contribution
1. Cloner le projet
2. Créer une nouvelle branche
3. Check out la branche
4. Commit et push du code
5. Créer un PR et alerter l'équipe

## Convention
* Le code et les commentaires seront de préférence en Français
* On utilisera Python 3.7
* Le linter sera PyLint

## Documentation
[Schema des classes](https://drive.google.com/drive/folders/1uquCE7LE1dYdJEXwpesMFMWH9KIWeSem?usp=sharing)