DASK Felleskomponenter
This is a repo where we make available governance components, common functions and reusable UDFs. DASK felleskomponenter is still in an early stage of the development process.
You can find the PyPI package here.
Dependencies
You need to install Python 3.7 and higher, and to install the dependencies of this project, please execute the following command
pip install -r requirements.txt
Code formatting
The python code is validated against Black formatting in a Github Action. This means that your pull request will fail if the code isn't formatted according to Black standards. It is therefore suggested to enable automatic formatting using Black in your IDE.
Bulding and publishing of package
Publishing using GitHub Actions
Navigate to the Publish to PyPI workflow in GitHub Actions, choose the main branch and bump the version.
The workflow is authenticated through Trusted Publisher. The workflow can push to either TestPyPI or PyPI depending on the given input.
You can choose to not commit the changed version number to github. This is useful if you are doing testing to avoid cleaning up commits.
One member of Team DASK needs to approve the workflow before it can publish to PyPI.
Manual publishing to PyPI
To do manual publishing you will need to provide the user credentials of a user with publishing access to the dask-felleskomponenter package on PyPI.
- Remove old dist-folder, from last time you published
- Update version in
setup.py, for instance0.0.7->0.0.8 - (Run
pip install -r requirements.txtif you haven't done that earlier) - Run
python3 -m build(and wait some minutes...) - Verify that dist contains a package with the new version in the package name.
- Run
python3 -m twine upload dist/*to upload to PyPi
Manual publishing to TestPyPI
To do manual publishing you will need to provide the user credentials of a user with publishing access to the dask-felleskomponenter package on TestPyPI.
To do a manual publish to TestPyPI do steps 1 through 5 for publishing to PyPI, and finish using the command python3 -m twine upload --repository testpypi dist/*
Run tests
Use the following command
coverage run -m unittest discover -s src/dask_felleskomponenter/tests
coverage report -m
3 maintainers
Metadata
3 maintainers
Release files for dask-felleskomponenter 0.2.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 | |
|---|---|---|---|
| dask_felleskomponenter-0.2.0.tar.gz | 23.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dask_felleskomponenter-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 54.8 kB
Release files / dask_felleskomponenter-0.2.0.tar.gz
| Download URL | dask_felleskomponenter-0.2.0.tar.gz |
|---|---|
| Size | 23.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bbd39fdb1e79e472c4aa2268cc3d76218db40e1cf382f381dc7cd36fa0478bc5
|
|
BLAKE2b-256 checksum How to use checksums |
efeb29840c97304c8843c1b3b5326dadba39a842a80ae44477c9faf326cb2392
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 18, 2026.
Transparency logRelease files / dask_felleskomponenter-0.2.0-py3-none-any.whl
| Download URL | dask_felleskomponenter-0.2.0-py3-none-any.whl |
|---|---|
| Size | 30.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f0619ec47ee9388ed088f8cc1621a8515e0b77d870c2bc59abb427f2b146125f
|
|
BLAKE2b-256 checksum How to use checksums |
ef15ee49b3220b68cad35fa05ebd194381542a6b7ab67105678a0ec551c72131
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 18, 2026.
Transparency log
