Development environment initialization
for the Daipe stack
What it does
Local Computer
- Extends the Pyfony dev environment initialization
- Downloads Hadoop's
winutils.exeand puts it into the project's.venvdirectory (Windows only) - Downloads Java 1.8 binaries and puts them into the
~/.databricks-connect-javadir - Creates the empty
~/.databricks-connectfile
Databricks Repos Environment
- Download and install poetry package manager
- Install dependencies from poetry.lock
- Set current working directory to project root
- Append src folder to sys path
- Set proper environment variables
Usage
%sh
pip install benvy==1.3.3
from benvy.databricks.repos import bootstrap # noqa
bootstrap.install()
from benvy.databricks.repos import bootstrap # noqa
bootstrap.setup_env()
Metadata
Release files for benvy 1.4.8
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| benvy-1.4.8-py3-none-any.whl | Python 3 | none | any | Details for benvy-1.4.8-py3-none-any.whl |
Release files / benvy-1.4.8-py3-none-any.whl
| Download URL | benvy-1.4.8-py3-none-any.whl |
|---|---|
| Size | 78.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e9e7cc54b87b51b6b255804d0024bf00b2b5b563fc3c9b038f2c1b9ea430161b
|
|
BLAKE2b-256 checksum How to use checksums |
2825a76af1fd3ddde67652819922a440d975069b50b1e91c0022a8a427373b3e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.5.1 CPython/3.8.18 Linux/6.5.0-1025-azure
|
Security for benvy 1.4.8
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.