Dask-Snowflake
Installation
dask-snowflake can be installed with pip:
pip install dask-snowflake
or with conda:
conda install -c conda-forge dask-snowflake
Usage
dask-snowflake provides read_snowflake and to_snowflake methods
for parallel IO from Snowflake with Dask.
>>> from dask_snowflake import read_snowflake
>>> example_query = '''
... SELECT *
... FROM SNOWFLAKE_SAMPLE_DATA.TPCH_SF1.CUSTOMER;
... '''
>>> ddf = read_snowflake(
... query=example_query,
... connection_kwargs={
... "user": "...",
... "password": "...",
... "account": "...",
... },
... )
>>> from dask_snowflake import to_snowflake
>>> to_snowflake(
... ddf,
... name="my_table",
... connection_kwargs={
... "user": "...",
... "password": "...",
... "account": "...",
... },
... )
See their docstrings for further API information.
Tests
Running tests requires a Snowflake account and access to a database.
The test suite will automatically look for specific SNOWFLAKE_*
environment variables (listed below) that must be set.
It's recommended (though not required) to store these environment variables
in a local .env file in the root of the dask-snowflake repository.
This file will be automatically ignored by git, reducing the risk of accidentally
commiting it.
Here's what an example .env file looks like:
SNOWFLAKE_USER="<test user name>"
SNOWFLAKE_PASSWORD="<test_user_password>"
SNOWFLAKE_ACCOUNT="<account>.<region>.aws"
SNOWFLAKE_WAREHOUSE="<test warehouse>"
SNOWFLAKE_ROLE="<test role>"
SNOWFLAKE_DATABASE="<test database>"
SNOWFLAKE_SCHEMA="<test schema>"
You may then source .env or install pytest-dotenv
to automatically set these environment variables.
Note: If you run the tests and get an
MemoryErrormentioning "write+execute memory for ffi.callback()", you probably have stale build ofcffifrom conda-forge. Remove it and install the version usingpip:conda remove cffi --force pip install cffi
License
Metadata
Release files for dask-snowflake 0.3.4
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-snowflake-0.3.4.tar.gz | 13.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dask_snowflake-0.3.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 22.6 kB
Release files / dask-snowflake-0.3.4.tar.gz
| Download URL | dask-snowflake-0.3.4.tar.gz |
|---|---|
| Size | 13.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0b415ebfc8bc70ab388ea0f47728d1e87559ad3db219ca79ee87e9f8060d68ef
|
|
BLAKE2b-256 checksum How to use checksums |
f60b131e7bd95b07970e9c43089a837f8742c1d1ee4d423e569a437fa5093a61
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 Aug 4, 2025.
Transparency logRelease files / dask_snowflake-0.3.4-py3-none-any.whl
| Download URL | dask_snowflake-0.3.4-py3-none-any.whl |
|---|---|
| Size | 9.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3f4b4a2472c34962a8ad20969d5aae60910141b6dee77d1c2f8f17ee158c79a5
|
|
BLAKE2b-256 checksum How to use checksums |
52661ef9afc8fd0c3752c482d707e376f226c39f433f044d38c2df9fcd500156
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 Aug 4, 2025.
Transparency log