# sp3 & edgex_access
## sp3
Access to AWS S3 using Python3
S3 configuration for multiple S3 stores like minio, zenko, cloudian and nexentaedge
Very simple to use as a CLI
`bash % sp3 --copy -r myhome://photos/cabo/ aws3://photos/cabo `
`bash % sp3 --delete -r myhome://photos/cabo/ `
Please refer to [README_SP3.md](https://github.com/nacharya/edgex_access/blob/master/README_SP3.md) for details.
## edgex_access
A Python3 connector library that uses the AWS S3 protocol to access data storage
Provides a primary I/O library API that allows access to all platforms
Access to different Stores, Config, DataAccess and basic elements for I/O access and object access
Core API Objects like EdgexConfig, EdgexObject, EdgexDataAccess, EdgexAccess, EdgexHash that hides the underlying implemention of S3 and other proprietary access
Please refer to [README_EDGEX_ACCESS.md](https://github.com/nacharya/edgex_access/blob/master/README_EDGEX_ACCESS.md) for details.
### Prerequisites & Requirements
You need Python 3.5 or later to use edgex_access. You can have multiple Python versions (2.x and 3.x) installed on the same system without problems.
In Ubuntu, you can install Python 3 like this:
$ sudo apt-get install python3 python3-pip
Make sure you have Python3 installed. Please check the requirement.txt for a list of Python packages that should be pre-installed before edgex_access and s3p can be used.
### Installation
`bash % pip install edgex_access `
### Coding Style
The Hitchhiker’s Guide to Python [ http://docs.python-guide.org/en/latest/writing/style/ ]
## Authors
nexenta - Initial work - [edgex_pyconnector](https://github.com/Nexenta/edgex_pyconnector )
## License
This project is licensed under the MIT License - see the [LICENSE.md](LICENSE.md) file for details
## Acknowledgments
Thanks to dyusupov
Metadata
Release files for edgex-access 0.0.14
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 |
|---|---|---|---|---|
| edgex_access-0.0.14.tar.gz | 18.3 kB | Without provenance | Details for edgex_access-0.0.14.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| edgex_access-0.0.14-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for edgex_access-0.0.14-py2.py3-none-any.whl |
Total release size: 40.1 kB
Release files / edgex_access-0.0.14.tar.gz
| Download URL | edgex_access-0.0.14.tar.gz |
|---|---|
| Size | 18.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bde599039d27ab073677fc5c50a40df5641f4ad1afc5d8dd6b3c00d38430e6f9
|
|
BLAKE2b-256 checksum How to use checksums |
f9949fb5c12216d68bfc8c7121753b4b93d65b15bdbddcc5bf43677fa28fde49
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.20.1 setuptools/40.6.3 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/3.6.7
|
Release files / edgex_access-0.0.14-py2.py3-none-any.whl
| Download URL | edgex_access-0.0.14-py2.py3-none-any.whl |
|---|---|
| Size | 21.9 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
b816d80d584f40a861cb427f75b00157a4b2c56d1e9688a7628ffa82f5fc43ee
|
|
BLAKE2b-256 checksum How to use checksums |
ba845c230b943bb53ae33fe34fab080c6543dd7e843f1762c408106319f035eb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.20.1 setuptools/40.6.3 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/3.6.7
|
Security for edgex-access 0.0.14
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.