toolbox-pyspark
Introduction
The purpose of this package is to provide some helper files/functions/classes for generic PySpark processes.
Key URLs
For reference, these URL's are used:
| Type | Source | URL |
|---|---|---|
| Git Repo | GitHub | https://github.com/data-science-extensions/toolbox-pyspark |
| Python Package | PyPI | https://pypi.org/project/toolbox-pyspark |
| Package Docs | Pages | https://data-science-extensions.com/toolbox-pyspark |
Installation
You can install and use this package multiple ways by using any of your preferred methods: pip, pipenv, poetry, or uv.
Using pip:
-
In your terminal, run:
python3 -m pip install --upgrade pip python3 -m pip install toolbox-pyspark
-
Or, in your
requirements.txtfile, add:toolbox-pyspark
Then run:
python3 -m pip install --upgrade pip python3 -m pip install --requirement=requirements.txt
Using pipenv:
-
Install using environment variables:
In your
Pipfilefile, add:[[source]] url = "https://pypi.org/simple" verify_ssl = false name = "pypi" [packages] toolbox-pyspark = "*"
Then run:
python3 -m pip install pipenv python3 -m pipenv install --verbose --skip-lock --categories=root index=pypi toolbox-pyspark
-
Or, in your
requirements.txtfile, add:toolbox-pyspark
Then run:
python3 -m run pipenv install --verbose --skip-lock --requirements=requirements.txt
-
Or just run this:
python3 -m pipenv install --verbose --skip-lock toolbox-pyspark
Using poetry:
-
In your
pyproject.tomlfile, add:[project] dependencies = [ "toolbox-pyspark==1.*", ]
Then run:
poetry sync poetry install
-
Or just run this:
poetry add "toolbox-pyspark==1.*" poetry sync poetry install
Using uv:
-
In your
pyproject.tomlfile, add:[project] dependencies = [ "toolbox-pyspark==1.*", ]
Then run:
uv sync -
Or run this:
uv add "toolbox-pyspark==1.*" uv sync
-
Or just run this:
uv pip install "toolbox-pyspark==1.*"
Contribution
Check the CONTRIBUTING.md file or Contributing page.
Metadata
Release files for toolbox-pyspark 1.2.1
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 |
|---|---|---|---|---|
| toolbox_pyspark-1.2.1.tar.gz | 72.6 kB | Without provenance | Details for toolbox_pyspark-1.2.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| toolbox_pyspark-1.2.1-py3-none-any.whl | Python 3 | none | any | Details for toolbox_pyspark-1.2.1-py3-none-any.whl |
Total release size: 157.2 kB
Release files / toolbox_pyspark-1.2.1.tar.gz
| Download URL | toolbox_pyspark-1.2.1.tar.gz |
|---|---|
| Size | 72.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4c81a1b532e121691b08d9cb36cec3a50e25c785f9311b0b619711491f588107
|
|
BLAKE2b-256 checksum How to use checksums |
406d437c65ae27a9ae510801614ac3facaf024c0566579d54fd38368003382b7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.0.1 CPython/3.13.1 Linux/6.8.0-1020-azure
|
Release files / toolbox_pyspark-1.2.1-py3-none-any.whl
| Download URL | toolbox_pyspark-1.2.1-py3-none-any.whl |
|---|---|
| Size | 84.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e490088aadb5edb0ec940c2b88b8a7873900f8bdf33ea134561e811624792b64
|
|
BLAKE2b-256 checksum How to use checksums |
fe7c30b572ad2da09e94197c78bc1549337e61ae7c2278d209fd7b9e45c519e1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.0.1 CPython/3.13.1 Linux/6.8.0-1020-azure
|
Security for toolbox-pyspark 1.2.1
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.