All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
IMPORTANT: Currently the project is in the initial development phase, this is why releases are marked as 0.z.y.
(following semantic versioning 2.0.0: "Major version zero (0.y.z) is for initial development.
Anything MAY change at any time. The public API SHOULD NOT be considered stable."). While in this phase, we will denote
breaking changes with a minor increase.
- Added support for python
3.12and3.13
- Bump all dependencies to the latest version and introduce necessary adaptation in the source code (affecting only
dac info):build~=0.9->build~=1.2toml~=0.10->toml~=0.10.2typer[all]~=0.7->typer~=0.15.2wheel~=0.38->wheel~=0.45
- Prevent installation with python >
3.13
dac next-versionis able to find the existing version of a package irrespectively of the use of-or_as a separator.
- Introduce
dac next-versioncommand, that allows to find the next minor release for a given python package and (optionally) a given major version.
- The
loadfunction inload.pycan contain optional arguments. Previously no arguments were allowed. load.pyandschema.pyare publicly accessible underdac_pkg_name.loadanddac_pkg_name.schemarespectively. Previously they were marked as private modules, underdac_pkg_name._loadanddac_pkg_name._schema.Schemadoes not have to be apandera.DataFrameModelanymore, but any class that implements avalidatemethod (see the_input.interface.Validatorprotocol).dacdoes not rely onpydanticanymore, and usesdataclassinstead. Changes affectPackConfigandPyProjectConfig.
- Cleanup
- Extend compatibility to pydantic v1. Now
dacworks with both v1 and v2 of pydantic
- Update code to be compatible with pydantic v2 (no retro-compatibility with v1)
- Dependencies passed in CLI
--pkg-dependenciesorPyProjectConfigmust be separated by;or newline (previously was,or newline)
- First release of
dac