Slackest
About
Slackest is a full-featured Python interface for the Slack API.
Examples
from slackest import Slackest
slack = Slackest('<your-slack-api-token-goes-here>')
# Send a message to #general channel
slack.chat.post_message('#general', 'Hello fellow slackers!')
# Get users list
response = slack.users.list()
users = response.body['members']
# Upload a file
slack.files.upload('hello.txt')
# If you need to proxy the requests
proxy_endpoint = 'http://myproxy:3128'
slack = Slackest('<your-slack-api-token-goes-here>',
http_proxy=proxy_endpoint,
https_proxy=proxy_endpoint)
# Advanced: Use `request.Session` for connection pooling (reuse)
from requests.sessions import Session
with Session() as session:
slack = Slackest(token, session=session)
slack.chat.post_message('#general', 'All these requests')
slack.chat.post_message('#general', 'go through')
slack.chat.post_message('#general', 'a single https connection')
Installation
$ pip install slackest
CICD
This project uses AWS CodeBuild to build. CodeBuild uses a YAML-based file called builspec.yml that runs the appropriate commands.
A wheel and a source distribution is provided according to the buildspec.
Building Locally
For local build testing, use the local CodeBuild image. See this AWS blog post for more details.
$ git clone https://github.com/aws/aws-codebuild-docker-images.git
$ cd aws-codebuild-docker-images/ubuntu/python/3.7.1
$ docker build -t aws/codebuild/python:3.7.1 .
$ docker pull amazon/aws-codebuild-local:latest --disable-content-trust=false
$ wget https://raw.githubusercontent.com/aws/aws-codebuild-docker-images/master/local_builds/codebuild_build.sh && chmod +x codebuild_build.sh
$ ./codebuild_build.sh -i aws/codebuild/python:3.7.1 -a /tmp/codebuild/
Documentation
Slack API
Slackest
TODO
Test completion, full coverage
Metadata
Release files for slackest 0.15.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| slackest-0.15.0.tar.gz | 21.5 kB | Without provenance | Details for slackest-0.15.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| slackest-0.15.0-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for slackest-0.15.0-py2.py3-none-any.whl |
Total release size: 60.6 kB
Release files / slackest-0.15.0.tar.gz
| Download URL | slackest-0.15.0.tar.gz |
|---|---|
| Size | 21.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4d8d1a45731ce9ec6652be1064347106ededfde353d400826ad49659a4f147d8
|
|
BLAKE2b-256 checksum How to use checksums |
d8fec6baaf0a7df27204a3255370370ddb5c76cb483d915e8cd1f8edba72b2d7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.7.0 requests/2.22.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.7.3
|
Release files / slackest-0.15.0-py2.py3-none-any.whl
| Download URL | slackest-0.15.0-py2.py3-none-any.whl |
|---|---|
| Size | 39.1 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
412b8041acd810bc3bf6027c0b1e90d9cba848c3d10f313e21c0e05c19779ef5
|
|
BLAKE2b-256 checksum How to use checksums |
b192d75c3b52f62bd605bb35fa68c8122769a4611afa8075362664322db5e054
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.7.0 requests/2.22.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.7.3
|
Security for slackest 0.15.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.