fs_dlk
pyfilesystem2 interface to Azure Datalake
Installing
pip install fs-dlk
Opening FS Datalake
Authentication with username and password:
from fs_dlk import DLKFS
dlkfs = DLKFS("/path/to/the/remote/dir", username="username", password="password")Authentication with tenant secret:
from fs_dlk import DLKFS
dlkfs = DLKFS("/path/to/the/remote/dir", tenant_id="tenant id", client_id="client id", client_secret="client_secret")Specifying custom store name:
from fs_dlk import DLKFS
dlkfs = DLKFS("/path/to/the/remote/dir", store="store name", **auth_args_here)Authentication with connection strings:
Username and password auth:
import fs
dlkfs = fs.open_fs("dlk://username:password@/store_name/path/to/remote")Tenant secret auth:
import fs
dlkfs = fs.open_fs("dlk://username:password@tenant-id/store_name/path/to/remote")Downloading files
with open("local_file", "wb") as local_file:
dlkfs.download("path/to/remote/file", local_file)Uploading files
with open("local_file", "wb") as local_file:
dlkfs.upload("path/to/remote/file", local_file)1 maintainer
Metadata
1 maintainer
Release files for fs-dlk 0.1.3
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 |
|---|---|---|---|---|
| fs-dlk-0.1.3.tar.gz | 5.2 kB | Without provenance | Details for fs-dlk-0.1.3.tar.gz |
Release files / fs-dlk-0.1.3.tar.gz
| Download URL | fs-dlk-0.1.3.tar.gz |
|---|---|
| Size | 5.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
10791eaf2496c31e84847b6be91bac7e8b77a5694ae5b13c0900a85e624bad8e
|
|
BLAKE2b-256 checksum How to use checksums |
04c77b0b0907101c3bd69049b2bd344d8c24173a6507d493071c1f284d8944e9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/45.2.0 requests-toolbelt/0.9.1 tqdm/4.43.0 CPython/3.6.10
|
Security for fs-dlk 0.1.3
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.
