Metadata-Version: 2.4
Name: materialized-intelligence
Version: 0.1.2
Summary: Materialized Intelligence SDK
Project-URL: Homepage, https://materialized.dev
Project-URL: Documentation, https://docs.materialized.dev
License-Expression: Apache-2.0
License-File: LICENSE
Requires-Python: >=3.10
Requires-Dist: click==8.1.7
Requires-Dist: colorama==0.4.4
Requires-Dist: numpy==2.1.1
Requires-Dist: pandas==2.2.3
Requires-Dist: polars==1.8.2
Requires-Dist: requests==2.32.3
Requires-Dist: yaspin==3.1.0
Description-Content-Type: text/markdown

# materialized-client

The official Python client for Materialized Intelligence. See [docs.materialized.dev](https://docs.materialized.dev/) for more information.

## Installing Locally (to test changes during development)

Run `make install` from the root directory. This should remove the old builds and reinstall the package in your environment with the latest. You can run `uv pip list` to ensure the package is pointing at the local files instead of the PyPI package.

## Creating releases

Make sure you increment the version appropriately in `pyproject.toml`. Generally speaking we'll do patch versions for small tweaks, minor versions for large additions or changes to behavior, and probably do major releases once it makes sense. Since we're still in beta and `0.x.x` releases, its probably okay to add backwards-incompatible changes to minor releases, but we want to avoid this if possible. 

To create a release, run: 

`make release <version>` with `<version>` formatted like `0.1.1`

It'll prompt you for an API key to PyPI, which you must have for it to work. 

We also have a test PyPI account which you can use to test creating releases before pushing to the actual PyPI hub. I believe you can only create **one** release per version number, so it may be worth testing if you're paranoid about getting it right.

Also make sure to update the docs and increment the docs version number to match the new release. Keeping these consistent will provide a better user experience. 