semvec/pypi-packages huggingface dataset:
django-teams-community 1.4.5
This package provides a framework for organizing groups ofusers and restricting access in other views and models

django\_teams
=============

[![Build Status](https://travis-ci.org/CSDTs/django_teams.svg?branch=master)](https://travis-ci.org/CSDTs/django_teams)[![Updates](https://pyup.io/repos/github/CSDTs/django_teams/shield.svg)](https://pyup.io/repos/github/CSDTs/django_teams/)[![Coverage Status](https://coveralls.io/repos/github/CSDTs/django_teams/badge.svg?branch=master)](https://coveralls.io/github/CSDTs/django_teams?branch=master)

This project aims to provide an easy-to-use method for restricting row-based access to models based on "teams".
Teams control objects, and can specify who is allowed to read, create, update, and delete objects.

This repository originally written by chuck211991, modified for rpi_csdt_community.
imd-handler 0.0.422
Set of stuff for ingesting, discovery, editing and storing DG IMD files

# IMDiddler
A tool for editing IMD files either from local or s3
Can be deployed/invoked as a lambda or command line.
IMD file order is preserved. IMD edits can be in arbitrary order

### Editing Specifier
The edit to the imd is specified by a json string which maps the key/value pairs and simply replaces 
an existing key/value pair in the IMD file with the key/value pair in the json string. There's no limit on how
long you make the edit specifiers you can edit one or all the items in an IMD with a single specifier.
It is a simple overlaying operation. The one special consideration is for the 'BEGIN_GROUP/END_GROUP' pair, discussed below.
One can specify any of the types in the IMD. The following edits are for each of the individual types 
#####String
 ```javascript
'{"version": "\\"28.4\\";"}'
```
#####Integer
 ```javascript
'{"numRows": 6932;"}'
```
#####Date
 ```javascript
'{"generationTime": 2017-08-01T03:39:53.000000Z;"}'
```
You get the idea...

####Groups
IMDs contain a BEGIN_GROUP=<name> and END_GROUP=<name> for bands, images and products. The naming scheme is the disambiguator.
You can edit the contents of a group by specifying the name of the group within the IMD as a key and then a sub-dictionary
of key/value pairs to be applied within the group. The following edits the "IMAGE_1" group in the IMD, replacing the satellite name.
```javascript
'"IMAGE_1": {"satId": "\\"WV09\\";"}}'
```

### Invocation
The code can be invoked either via the command line or as a lambda. 

#### Command line
```commandline
python imd_handler.py <input file/s3 object> <edit[s]>
```
The input file is a file URI, self explanatory (any valid path, read/write access required)
```commandline
file:///Volumes/GKW/Sibinacocha2017/1cc99383-29fd-470a-a3ac-22431193b65a/103001006A803400/056848496010_01/056848496010_01_P001_MUL/17MAY12150511-M1BS-056848496010_01_P001.IMD
```

The s3 Object is an S3 URI specifying the bucket and path for the name ie:
```commandline
s3://727281582563-deliveries/production/I00000070198_01/I00000070198_01_P001_MUL/18APR05102137-M1BS_R1C1-I00000070198_01_P001.IMD
```

#### As a lambda
It's deployed as IMDiddler. The event dictionary/payload should look like:

```json
{
    "file_uri":  "<input file/s3 object>"
    "edit" : 
    {
        "<edit tag>" : "<edit value>"
    }
}
```

#####Lambda Example payload
```json
{
    "file_uri" :  "s3://727281582563-deliveries/production/I00000070198_01/I00000070198_01_P001_MUL/18APR05102137-M1BS_R1C1-I00000070198_01_P001.IMD"
    "edit" : 
    {
        "version": "\"28.4\";",
        "IMAGE_1": {"satId": "\"WV09;\""}
    }
}
```

#####Nota Bene:
 IMD Files contain quoted strings which means that the edits performed must also contain the quotes. 
 This means that the JSON quote escapement mechanism must be used for string types. Other types (float, int, date) do not
 need this.
asterisk_mbox_server 0.5.3
The server portion of a client/server to interact with Asterisk voicemail mailboxes
Keywords: testing

=================
AsteriskVM Server
=================
AsteriskVM is a client/server which provides an API to work with Asterisk voicemail mailboxes
This is the server code which needs to be installed on the Asterisk server and will monitor
mailbox directory for changes

Dependencies
============

* Linux >= 2.6.13
* Python >= 3.4
* Lame

Capabilities
============

* Display all metadata for all messages stored in a single mailbox
* Convert messages to text using Google's speech-to-text service
* Retrieve the audio of a message in MP3 format
* Support both synchronous and asynchronous API

Configuration
=============
Configuration is performed via the config.ini file

Parameters
----------
* **host** *(Optional)*: The IP address to listen on for client requests. This defaults to all IP addresses on the server. To listen only locally, choose 127.0.0.1
* **port** *(Optional)*: The port to listen on for client requests. Defaults to 12345.
* **password** *(Required)*: A password shared between client and server. Use only alpha-numeric characters and spaces
* **mbox_path** *(Required)*: The path to the storage location of mailbox files. This is typically /var/spool/asterisk/voicemail/default/<mailbox>/
* **cache_file** *(Required)*: A fully-qualified path to a file thht can be written by the server containing transcriptions of voicemails. Example: /var/spool/asterisk/transcription.cache
* **google_key** *(Required)*: Your 40 characters Google API key.
* **cdr** *(Optional)*: Where to find CDR data.  Supports various SQL databases as well as a file log.

Future work
============

* Support moving messages
* Support multiple mailboxes
* Support alternate text-to-speech providers