Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
0.6.0 (2026-03-18)
Features
PySpark is now an optional dependency (27e864b)
Users running PySpark in managed environments (Databricks, EMR, etc.) typically have PySpark
pre-installed and cannot or do not want the library to reinstall it. PySpark is now optional
and must be explicitly requested:
pandas,pydantic, andtabulateremain hard dependencies. Importingdataframe_expectationsno longer touches PySpark at all when it isn't installed — all PySpark imports are deferred
behind
@lru_cachehelpers that return a proxy raising a clearImportErroronly when aPySpark code path is actually executed.
PySpark tests isolated by marker (ef847ed)
All PySpark test cases are decorated with
@pytest.mark.pysparkand separated into their ownparametrize blocks.
--strict-markersis now enforced so unregistered markers cause animmediate failure. Tests can be run without PySpark present:
CI updated to cover three install scenarios
tests-without-pyspark-m "not pyspark"tests-with-pyspark-extrapip install .[pyspark]tests-with-external-pysparkThe
tests-with-external-pysparkjob specifically validates that the library works correctlywhen PySpark is already present in the environment and was not installed by this package.