pointblank 0.9.1__tar.gz → 0.9.2__tar.gz

{pointblank-0.9.1 → pointblank-0.9.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pointblank
-Version: 0.9.1
+Version: 0.9.2
 Summary: Find out if your data is what you think it is.
 Author-email: Richard Iannone <riannone@me.com>
 License: MIT License

{pointblank-0.9.1 → pointblank-0.9.2}/docs/_quarto.yml

@@ -133,6 +133,7 @@ quartodoc:
         - name: Validate.row_count_match
         - name: Validate.col_count_match
         - name: Validate.conjointly
+        - name: Validate.specially
     - title: Column Selection
       desc: >
         A flexible way to select columns for validation is to use the `col()` function along with

pointblank-0.9.2/docs/blog/all-about-actions/index.qmd

@@ -0,0 +1,434 @@
+---
+jupyter: python3
+html-table-processing: none
+title: "Level Up Your Data Validation with `Actions` and `FinalActions`"
+author: Rich Iannone
+date: 2025-05-02
+freeze: true
+---
+
+```{python}
+#| echo: false
+#| output: false
+import pointblank as pb
+pb.config(report_incl_footer=False)
+```
+
+Data validation is only useful if you can respond appropriately when problems arise. That's why
+Pointblank's recent `v0.8.0` and `v0.8.1` releases have significantly enhanced our action framework,
+allowing you to create sophisticated, automated responses to validation failures.
+
+In this post, we'll explore how to use:
+
+1. **Actions** to respond to individual validation failures
+2. **FinalActions** to execute code after your entire validation plan completes
+3. New customization features that make your validation workflows more expressive
+
+Let's dive into how these features can transform your data validation process from passive reporting
+to active response.
+
+## From Passive Validation to Active Response
+
+Traditional data validation simply reports problems: "Column X has invalid values." But what if you
+want to:
+
+- send a Slack message when critical errors occur?
+- log detailed diagnostics about failing data?
+- trigger automatic data cleaning processes?
+- generate custom reports for stakeholders?
+
+This is where Pointblank's action system can help. By pairing thresholds with actions, you can
+create automated responses that trigger exactly when needed.
+
+## Getting Started with Actions
+
+Actions are executed when validation steps fail to meet certain thresholds. Let's start with a
+simple example:
+
+```{python}
+import pointblank as pb
+
+validation_1 = (
+    pb.Validate(data=pb.load_dataset(dataset="small_table"))
+    .col_vals_gt(
+        columns="d",
+        value=1000,
+        thresholds=pb.Thresholds(warning=1, error=5),
+        actions=pb.Actions(
+            warning="⚠️ WARNING: Some values in column 'd' are below the minimum threshold!"
+        )
+    )
+    .interrogate()
+)
+
+validation_1
+```
+
+In this example:
+
+1. we're validating that values in column "d" are greater than 1000
+2. we set a warning threshold of 1 (triggers if any values fail)
+3. we define an action that prints a warning message when the threshold is exceeded
+
+Since several values in column `d` are below `1000`, our 'warning' action is triggered and the
+message appears above the validation report.
+
+## The Anatomy of Actions
+
+The [`Actions`](https://posit-dev.github.io/pointblank/reference/Actions.html) class is a very
+important piece of Pointblank's response system. Actions can be defined in several ways:
+
+1. **String messages**: simple text output to the console
+2. **Callable functions**: custom Python functions that execute when triggered
+3. **Lists of strings/callables**: multiple actions that execute in sequence
+
+Actions can be paired with different severity levels:
+
+- 'warning': for minor issues that need attention
+- 'error': for more significant problems
+- 'critical': for severe issues that require immediate action
+
+The `v0.8.0` release added two (very) useful new parameters:
+
+- `default=`: apply the same action to all threshold levels
+- `highest_only=`: only trigger the action for the highest threshold level reached (`True` by
+default)
+
+Let's see how these work in practice:
+
+```{python}
+def log_problem():
+    # Simple action that runs when thresholds are exceeded
+    print("A validation threshold has been exceeded!")
+
+validation_2 = (
+    pb.Validate(
+        data=pb.load_dataset(dataset="game_revenue"),
+        thresholds=pb.Thresholds(warning=0.05, error=0.10, critical=0.15),
+        actions=pb.Actions(default=log_problem)  # Apply this action to all threshold levels
+    )
+    .col_vals_regex(
+        columns="player_id",
+        pattern=r"[A-Z]{12}\d{3}"
+    )
+    .col_vals_gt(
+        columns="item_revenue",
+        value=0.10
+    )
+    .interrogate()
+)
+
+validation_2
+```
+
+In this example, we're using a simple function that prints a generic message whenever any threshold
+is exceeded. By using the `Actions(default=)` parameter, this same function gets applied to all
+threshold levels ('warning', 'error', and 'critical'). This saves you from having to define separate
+actions for each level when you want the same behavior for all of them. The `highest_only=`
+parameter (`True` by default, so not shown here) is complementary and it ensures that only the
+action for the highest threshold level reached will be triggered, preventing multiple notifications
+for the same validation failure.
+
+## Dynamic Messages with Templating
+
+Actions don't have to be static messages. With Pointblank's templating system, you can create
+context-aware notifications that include details about the specific validation failure.
+
+Available placeholders include:
+
+- `{type}`: the validation step type (e.g., `"col_vals_gt"`)
+- `{level}`: the threshold level ('warning', 'error', 'critical')
+- `{step}` or `{i}`: the step number in the validation workflow
+- `{col}` or `{column}`: the column name being validated
+- `{val}` or `{value}`: the comparison value used in the validation
+- `{time}`: when the action was executed
+
+You can also capitalize placeholders (like `{LEVEL}`) to get uppercase text.
+
+```{python}
+action_template = "[{LEVEL}] Step {step}: Values in '{column}' failed validation against {value}."
+
+validation_3 = (
+    pb.Validate(
+        data=pb.load_dataset(dataset="small_table"),
+        thresholds=pb.Thresholds(warning=1, error=4, critical=10),
+        actions=pb.Actions(default=action_template)
+    )
+    .col_vals_lt(
+        columns="d",
+        value=3000
+    )
+    .interrogate()
+)
+
+validation_3
+```
+
+This templating approach is a great way to create context-aware notifications that adapt to the
+specific validation failures occurring. As the example shows, when values in column `d` fail
+validation against the limit of `3000`, the template automatically generates a meaningful error
+message showing exactly which step, column, and threshold value was involved.
+
+## Accessing Metadata in Custom Action Functions
+
+For more sophisticated actions, you often need access to details about the validation failure. The
+`get_action_metadata()` function provides this context when called inside an action function:
+
+```{python}
+def send_detailed_alert():
+    # Get metadata about the validation failure
+    metadata = pb.get_action_metadata()
+
+    # Create a customized alert message
+    print(f"""
+    VALIDATION FAILURE DETAILS
+    -------------------------
+    Step: {metadata['step']}
+    Column: {metadata['column']}
+    Validation type: {metadata['type']}
+    Severity: {metadata['level']} (level {metadata['level_num']})
+    Time: {metadata['time']}
+
+    Explanation: {metadata['failure_text']}
+    """)
+
+validation_4 = (
+    pb.Validate(
+        data=pb.load_dataset(dataset="small_table"),
+        thresholds=pb.Thresholds(critical=1),
+        actions=pb.Actions(critical=send_detailed_alert)
+    )
+    .col_vals_gt(
+        columns="d",
+        value=5000
+    )
+    .interrogate()
+)
+
+validation_4
+```
+
+The metadata dictionary contains essential fields for a given validation step, including the step
+number, column name, validation type, severity level, and failure explanation. This gives you
+complete flexibility to create highly customized responses based on the specific nature of the
+validation failure.
+
+## Final Actions with `FinalActions`
+
+While regular [`Actions`](https://posit-dev.github.io/pointblank/reference/Actions.html) are great
+for responding to individual validation steps, sometimes you need to take action based on the
+overall validation results. This is where the new `FinalActions` feature from `v0.8.1` comes in.
+
+Unlike regular [`Actions`](https://posit-dev.github.io/pointblank/reference/Actions.html) that
+trigger during validation,
+[`FinalActions`](https://posit-dev.github.io/pointblank/reference/FinalActions.html) execute after
+all validation steps are complete.
+[`FinalActions`](https://posit-dev.github.io/pointblank/reference/FinalActions.html) accepts any
+number of actions (strings or callables) and executes them in sequence. Each argument can be a
+string message to display in the console, a callable function, or a list of strings/callables for
+multiple actions to execute in sequence.
+
+The real power of [`FinalActions`](https://posit-dev.github.io/pointblank/reference/FinalActions.html)
+comes from the ability to access comprehensive information about your validation results using
+[`get_validation_summary()`](https://posit-dev.github.io/pointblank/reference/get_validation_summary.html).
+When called inside a function passed to
+[`FinalActions`](https://posit-dev.github.io/pointblank/reference/FinalActions.html), this function
+provides a dictionary containing counts of passing/failing steps and test units, threshold levels
+exceeded, and much more:
+
+```{python}
+def generate_summary():
+    # Access comprehensive validation results
+    summary = pb.get_validation_summary()
+
+    print("\n=== VALIDATION SUMMARY ===")
+    print(f"Total steps: {summary['n_steps']}")
+    print(f"Passing steps: {summary['n_passing_steps']}")
+    print(f"Failing steps: {summary['n_failing_steps']}")
+
+    if summary['highest_severity'] == "critical":
+        print("\n⚠️ CRITICAL FAILURES DETECTED - immediate action required!")
+    elif summary['highest_severity'] == "error":
+        print("\n⚠️ ERRORS DETECTED - review needed")
+    elif summary['highest_severity'] == "warning":
+        print("\n⚠️ WARNINGS DETECTED - please investigate")
+    else:
+        print("\n✅ All validations passed!")
+
+validation_5 = (
+    pb.Validate(
+        data=pb.load_dataset(dataset="small_table"),
+        tbl_name="small_table",
+        thresholds=pb.Thresholds(warning=1, error=5, critical=10),
+        final_actions=pb.FinalActions(
+            "Validation process complete.",  # A simple string message
+            generate_summary               # Our function using get_validation_summary()
+        )
+    )
+    .col_vals_gt(columns="a", value=1)
+    .col_vals_lt(columns="d", value=10000)
+    .interrogate()
+)
+
+validation_5
+```
+
+The [`get_validation_summary()`](https://posit-dev.github.io/pointblank/reference/get_validation_summary.html)
+function is only available within functions passed to
+[`FinalActions`](https://posit-dev.github.io/pointblank/reference/FinalActions.html). It gives you
+access to these key dictionary fields:
+
+- `tbl_name`: name of the validated table
+- `n_steps`: total number of validation steps
+- `n_passing_steps`, n_failing_steps: count of passing/failing steps
+- `n`, `n_passed`, `n_failed`: total test units and their pass/fail counts
+- `highest_severity`: the most severe threshold level reached ('warning', 'error', 'critical')
+- and many more detailed statistics
+
+This information allows you to create detailed and specific final actions that can respond
+appropriately to the overall validation results.
+
+## Combining Regular and Final Actions
+
+You can use both [`Actions`](https://posit-dev.github.io/pointblank/reference/Actions.html) and
+[`FinalActions`](https://posit-dev.github.io/pointblank/reference/FinalActions.html) together for
+comprehensive control over your validation workflow:
+
+```{python}
+def step_alert():
+    metadata = pb.get_action_metadata()
+    print(f"Step {metadata['step']} failed with {metadata['level']} severity")
+
+
+def final_summary():
+    summary = pb.get_validation_summary()
+
+    # Get counts by checking each step's status in the dictionaries
+    steps = range(1, summary['n_steps'] + 1)
+    n_critical = sum(1 for step in steps if summary['dict_critical'].get(step, False))
+    n_error = sum(1 for step in steps if summary['dict_error'].get(step, False))
+    n_warning = sum(1 for step in steps if summary['dict_warning'].get(step, False))
+
+    print(f"\nValidation complete with:")
+    print(f"- {n_critical} critical issues")
+    print(f"- {n_error} errors")
+    print(f"- {n_warning} warnings")
+
+
+validation_6 = (
+    pb.Validate(
+        data=pb.load_dataset(dataset="small_table"),
+        thresholds=pb.Thresholds(warning=1, error=5, critical=10),
+        actions=pb.Actions(default=step_alert),
+        final_actions=pb.FinalActions(final_summary),
+    )
+    .col_vals_gt(columns="a", value=5)
+    .col_vals_lt(columns="d", value=1000)
+    .interrogate()
+)
+
+validation_6
+```
+
+This approach allows you to log individual step failures during the validation process using
+[`Actions`](https://posit-dev.github.io/pointblank/reference/Actions.html) and generate a
+comprehensive report after all validation steps are complete using
+[`FinalActions`](https://posit-dev.github.io/pointblank/reference/FinalActions.html). Using both
+action types gives you fine-grained control over when and how notifications and other actions are
+triggered in your validation workflow.
+
+## Real-World Example: Building an Automated Validation Pipeline
+
+Let's put everything together in a more realistic example. Imagine you're validating a gaming
+revenue dataset and want to:
+
+1. log detailed information about each failure
+2. send a Slack notification if critical failures occur
+3. generate a comprehensive report after validation completes
+
+```{python}
+def log_step_failure():
+    metadata = pb.get_action_metadata()
+    print(f"[{metadata['level'].upper()}] Step {metadata['step']}: {metadata['failure_text']}")
+
+def analyze_results():
+    summary = pb.get_validation_summary()
+
+    # Calculate overall pass rate
+    pass_rate = (summary['n_passing_steps'] / summary['n_steps']) * 100
+
+    print(f"\n==== VALIDATION RESULTS ====")
+    print(f"Table: {summary['tbl_name']}")
+    print(f"Pass rate: {pass_rate:.2f}%")
+    print(f"Failing steps: {summary['n_failing_steps']} of {summary['n_steps']}")
+
+    # In a real scenario, here you might:
+    # 1. Save results to a database
+    # 2. Generate and email an HTML report
+    # 3. Trigger data cleansing workflows
+
+    # Simulate a Slack notification
+    if summary['highest_severity'] == "critical":
+        print("\n🚨 [SLACK NOTIFICATION] Critical data quality issues detected!")
+        print("@data-team Please investigate immediately.")
+
+# Create our validation workflow with actions
+validation_7 = (
+    pb.Validate(
+        data=pb.load_dataset(dataset="game_revenue"),
+        tbl_name="game_revenue",
+        thresholds=pb.Thresholds(warning=0.05, error=0.10, critical=0.15),
+        actions=pb.Actions(default=log_step_failure, highest_only=True),
+        final_actions=pb.FinalActions(analyze_results),
+        brief=True  # Add automatically-generated briefs
+    )
+    .col_vals_regex(
+        columns="player_id",
+        pattern=r"[A-Z]{12}\d{3}",
+        brief="Player IDs must follow standard format"  # Custom brief text
+    )
+    .col_vals_gt(
+        columns="item_revenue",
+        value=0.10
+    )
+    .col_vals_gt(
+        columns="session_duration",
+        value=15
+    )
+    .interrogate()
+)
+
+validation_7
+```
+
+## Wrapping Up: from Passive Validation to Active Data Quality Management
+
+With [`Actions`](https://posit-dev.github.io/pointblank/reference/Actions.html) and
+[`FinalActions`](https://posit-dev.github.io/pointblank/reference/FinalActions.html), Pointblank is
+now more of a complete data quality management system. Instead of just detecting problems, you can
+now:
+
+1. respond immediately to validation failures
+2. customize responses based on severity level
+3. generate comprehensive reports after validation completes
+4. integrate with other systems through custom action functions
+5. automate workflows based on validation results
+
+These capabilities transform data validation from a passive reporting activity into an active
+component of your data pipeline, helping ensure that data quality issues are detected, reported, and
+addressed efficiently.
+
+As we continue to enhance Pointblank, we'd love to hear how you're using
+[`Actions`](https://posit-dev.github.io/pointblank/reference/Actions.html) and
+[`FinalActions`](https://posit-dev.github.io/pointblank/reference/FinalActions.html) in your
+workflows. Share your experiences or suggestions with us on
+[Discord](https://discord.gg/YH7CybCNCQ) or file an issue on
+[GitHub](https://github.com/posit-dev/pointblank/issues).
+
+## Learn More
+
+Explore our documentation to learn more about Pointblank's action capabilities:
+
+- [Actions documentation](https://posit-dev.github.io/pointblank/reference/Actions.html)
+- [FinalActions documentation](https://posit-dev.github.io/pointblank/reference/FinalActions.html)
+- [User Guide on Triggering Actions](https://posit-dev.github.io/pointblank/user-guide/actions.html)

{pointblank-0.9.1 → pointblank-0.9.2}/pointblank/_constants.py

@@ -44,6 +44,7 @@ ASSERTION_TYPE_METHOD_MAP = {
     "row_count_match": "row_count_match",
     "col_count_match": "col_count_match",
     "conjointly": "conjointly",
+    "specially": "specially",
 }
 
 METHOD_CATEGORY_MAP = {
@@ -69,6 +70,7 @@ METHOD_CATEGORY_MAP = {
     "row_count_match": "ROW_COUNT_MATCH",
     "col_count_match": "COL_COUNT_MATCH",
     "conjointly": "CONJOINTLY",
+    "specially": "SPECIALLY",
 }
 
 COMPARISON_OPERATORS = {
@@ -455,6 +457,18 @@ SVG_ICONS_FOR_ASSERTION_TYPES = {
             <path d="M51.8485976,12 L15.5758703,12 C13.9986329,12 12.712234,13.2863989 12.712234,14.8636364 L12.712234,51.1363636 C12.712234,52.7136011 13.9986329,54 15.5758703,54 L51.8485976,54 C53.4258351,54 54.712234,52.7136011 54.712234,51.1363636 L54.712234,14.8636364 C54.712234,13.2863989 53.4258351,12 51.8485976,12 Z M37.072234,44 L20.272234,44 L20.272234,42 L37.072234,42 L37.072234,44 Z M37.072234,34 L20.272234,34 L20.272234,32 L37.072234,32 L37.072234,34 Z M37.072234,24 L20.272234,24 L20.272234,22 L37.072234,22 L37.072234,24 Z M47.9233279,41.773438 L45.5706719,45.773438 C45.4427029,45.996094 45.239265,46.148438 45.0095779,46.1875 C44.9702029,46.195313 44.9275469,46.199219 44.88489,46.199219 C44.70114,46.199219 44.5206719,46.128906 44.373015,45.992188 L42.1877029,43.992188 C41.8202029,43.65625 41.7512969,43.027344 42.033484,42.589844 C42.3156719,42.152344 42.8439529,42.070313 43.2114529,42.40625 L44.697859,43.769531 L46.548484,40.625 C46.814265,40.171875 47.335984,40.0625 47.716609,40.378906 C48.097234,40.695313 48.189109,41.320313 47.9233279,41.773438 Z M47.9233279,31.773438 L45.5706719,35.773438 C45.4427029,35.996094 45.239265,36.148438 45.0095779,36.1875 C44.9702029,36.195313 44.9275469,36.199219 44.88489,36.199219 C44.70114,36.199219 44.5206719,36.128906 44.373015,35.992188 L42.1877029,33.992188 C41.8202029,33.65625 41.7512969,33.027344 42.033484,32.589844 C42.3156719,32.152344 42.8439529,32.070313 43.2114529,32.40625 L44.697859,33.769531 L46.548484,30.628906 C46.814265,30.175781 47.335984,30.0625 47.716609,30.382813 C48.097234,30.699219 48.189109,31.320313 47.9233279,31.773438 Z M47.9233279,21.773438 L45.5706719,25.773438 C45.4427029,25.996094 45.239265,26.148438 45.0095779,26.1875 C44.9702029,26.195313 44.9275469,26.199219 44.88489,26.199219 C44.70114,26.199219 44.5206719,26.128906 44.373015,25.992188 L42.1877029,23.992188 C41.8202029,23.65625 41.7512969,23.027344 42.033484,22.589844 C42.3156719,22.152344 42.8439529,22.070313 43.2114529,22.40625 L44.697859,23.769531 L46.548484,20.625 C46.814265,20.171875 47.335984,20.0625 47.716609,20.378906 C48.097234,20.699219 48.189109,21.320313 47.9233279,21.773438 Z" id="conjoint" fill="#000000" fill-rule="nonzero"></path>
         </g>
     </g>
+</svg>""",
+    "specially": """<?xml version="1.0" encoding="UTF-8"?>
+<svg width="67px" height="67px" viewBox="0 0 67 67" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
+    <title>specially</title>
+    <g id="All-Icons" stroke="none" stroke-width="1" fill="none" fill-rule="evenodd">
+        <g id="specially" transform="translate(0.000000, 0.206897)">
+            <path d="M56.712234,1 C59.1975153,1 61.4475153,2.00735931 63.076195,3.63603897 C64.7048747,5.26471863 65.712234,7.51471863 65.712234,10 L65.712234,10 L65.712234,65 L10.712234,65 C8.22695259,65 5.97695259,63.9926407 4.34827294,62.363961 C2.71959328,60.7352814 1.71223397,58.4852814 1.71223397,56 L1.71223397,56 L1.71223397,10 C1.71223397,7.51471863 2.71959328,5.26471863 4.34827294,3.63603897 C5.97695259,2.00735931 8.22695259,1 10.712234,1 L10.712234,1 Z" id="rectangle" stroke="#000000" stroke-width="2" fill="#FFFFFF"></path>
+            <g id="star" transform="translate(8.500000, 8.500000)" fill="#000000" fill-rule="nonzero">
+                <path d="M25,0 C24.5874484,0 24.2174517,0.254002847 24.068359,0.6386719 L17.902344,16.535156 L0.94921875,17.400391 C0.536124409,17.4213013 0.17852458,17.6943523 0.0495446395,18.0873515 C-0.0794353012,18.4803507 0.046820452,18.9122002 0.3671875,19.173828 L13.568359,29.966797 L9.2324219,46.34375 C9.12646963,46.7428009 9.27663058,47.1659433 9.61042698,47.4089402 C9.94422338,47.651937 10.3930345,47.664834 10.740234,47.441406 L25,38.289062 L39.259766,47.441406 C39.6069655,47.6648339 40.0557766,47.6519369 40.3895729,47.4089401 C40.7233693,47.1659432 40.8735302,46.7428009 40.767578,46.34375 L36.431641,29.966797 L49.632812,19.173828 C49.953179,18.9122002 50.0794348,18.4803507 49.9504549,18.0873516 C49.821475,17.6943524 49.4638753,17.4213014 49.050781,17.400391 L32.097656,16.535156 L25.931641,0.6386719 C25.7825483,0.254002847 25.4125516,0 25,0 Z M25,3.7636719 L30.466797,17.861328 C30.609689,18.2291416 30.9554962,18.4785515 31.349609,18.498047 L46.359375,19.265625 L34.667969,28.826172 C34.3646054,29.0742114 34.2340493,29.4765679 34.333984,29.855469 L38.175781,44.369141 L25.541016,36.257812 C25.2114789,36.0458536 24.7885211,36.0458536 24.458984,36.257812 L11.824219,44.369141 L15.666016,29.855469 C15.7659507,29.4765679 15.6353946,29.0742114 15.332031,28.826172 L3.640625,19.265625 L18.650391,18.498047 C19.0445038,18.4785515 19.390311,18.2291416 19.533203,17.861328 L25,3.7636719 Z" id="Shape"></path>
+            </g>
+        </g>
+    </g>
 </svg>""",
 }
 

{pointblank-0.9.1 → pointblank-0.9.2}/pointblank/_constants_translations.py

@@ -1160,6 +1160,60 @@ EXPECT_FAIL_TEXT = {
         "hi": "असफल परीक्षण इकाइयों की अधिकता जहां संयुक्त 'पास' इकाइयां होनी चाहिए थीं।",
         "el": "Υπέρβαση αποτυχημένων μονάδων δοκιμής όπου θα έπρεπε να υπάρχουν κοινές μονάδες 'επιτυχίας'.",
     },
+    "specially_expectation_text": {
+        "en": "Expect that special testing with a given function yields agreement.",
+        "fr": "On s'attend à ce que les tests spéciaux avec une fonction donnée produisent un accord.",
+        "de": "Erwarten Sie, dass spezielle Tests mit einer bestimmten Funktion Übereinstimmung ergeben.",
+        "it": "Aspettati che i test speciali con una funzione data producano accordo.",
+        "es": "Se espera que las pruebas especiales con una función dada produzcan concordancia.",
+        "pt": "Espera-se que testes especiais com uma função dada produzam concordância.",
+        "ro": "Se așteaptă ca testarea specială cu o funcție dată să producă acord.",
+        "tr": "Belirli bir fonksiyonla özel testlerin uyum sağlamasını bekleyin.",
+        "zh-Hans": "预期使用给定函数的特殊测试会产生一致结果。",
+        "zh-Hant": "預期使用給定函數的特殊測試會產生一致結果。",
+        "ja": "指定された関数による特別なテストが一致することを期待します。",
+        "ko": "주어진 함수로 특수 테스트를 수행하면 일치함을 기대합니다.",
+        "vi": "Kỳ vọng rằng kiểm tra đặc biệt với một hàm đã cho sẽ cho kết quả phù hợp.",
+        "ru": "Ожидайте, что специальное тестирование с заданной функцией дает согласие.",
+        "cs": "Očekává se, že speciální testování s danou funkcí přinese shodu.",
+        "pl": "Oczekuj, że specjalne testowanie z użyciem danej funkcji przyniesie zgodność.",
+        "da": "Forvent at speciel test med en given funktion giver overensstemmelse.",
+        "sv": "Förvänta dig att speciell testning med en given funktion ger överensstämmelse.",
+        "nb": "Forvent at spesiell testing med en gitt funksjon gir samsvar.",
+        "nl": "Verwacht dat speciale tests met een gegeven functie overeenstemming opleveren.",
+        "fi": "Odota, että erityinen testaus annetulla funktiolla tuottaa yhdenmukaisuuden.",
+        "is": "Væntir þess að sérstök prófun með gefnu falli leiði til samræmis.",
+        "ar": "توقع أن الاختبار الخاص بدالة معينة يؤدي إلى التوافق.",
+        "hi": "अपेक्षा है कि दिए गए फ़ंक्शन के साथ विशेष परीक्षण सहमति प्रदान करेगा।",
+        "el": "Αναμένεται ότι ο ειδικός έλεγχος με μια δεδομένη συνάρτηση αποδίδει συμφωνία.",
+    },
+    "specially_failure_text": {
+        "en": "Exceedance of failed test units when performing specialized testing with a given function.",
+        "fr": "Dépassement des unités de test ayant échoué lors de l'exécution de tests spécialisés avec une fonction donnée.",
+        "de": "Überschreitung fehlgeschlagener Testeinheiten bei der Durchführung spezialisierter Tests mit einer bestimmten Funktion.",
+        "it": "Superamento delle unità di test fallite durante l'esecuzione di test specializzati con una funzione data.",
+        "es": "Se superó el número de unidades de prueba fallidas al realizar pruebas especializadas con una función dada.",
+        "pt": "Excedeu o número de unidades de teste com falha ao realizar testes especializados com uma função dada.",
+        "ro": "Depășirea unităților de test eșuate la efectuarea testării specializate cu o funcție dată.",
+        "tr": "Belirli bir fonksiyonla özel testler yapılırken başarısız test birimlerinin aşılması.",
+        "zh-Hans": "使用给定函数进行专门测试时，失败的测试单元数量超标。",
+        "zh-Hant": "使用給定函數進行專門測試時，失敗的測試單元數量超標。",
+        "ja": "指定された関数を使用した特殊テスト実行時のテスト単位の失敗の超過。",
+        "ko": "주어진 함수로 특수 테스트를 수행할 때 실패한 테스트 단위 초과.",
+        "vi": "Vượt quá số đơn vị kiểm tra thất bại khi thực hiện kiểm tra chuyên biệt với một hàm đã cho.",
+        "ru": "Превышение неудачных тестовых единиц при выполнении специализированного тестирования с заданной функцией.",
+        "cs": "Překročení počtu neúspěšných testovacích jednotek při provádění specializovaného testování s danou funkcí.",
+        "pl": "Przekroczenie nieudanych jednostek testowych podczas przeprowadzania specjalistycznych testów z daną funkcją.",
+        "da": "Overskridelse af fejlslagne testenheder ved udførelse af specialiseret test med en given funktion.",
+        "sv": "Överskrider antalet misslyckade testenheter vid utförande av specialiserad testning med en given funktion.",
+        "nb": "Overskridelse av mislykkede testenheter ved utførelse av spesialisert testing med en gitt funksjon.",
+        "nl": "Overschrijding van mislukte testeenheden bij het uitvoeren van gespecialiseerde tests met een gegeven functie.",
+        "fi": "Epäonnistuneiden testiyksiköiden ylitys suoritettaessa erikoistestejä annetulla funktiolla.",
+        "is": "Of mörg misheppnuð próf við framkvæmd sérhæfðra prófana með gefnu falli.",
+        "ar": "تجاوز وحدات الاختبار الفاشلة عند إجراء اختبار متخصص بدالة معينة.",
+        "hi": "दिए गए फ़ंक्शन के साथ विशेष परीक्षण करते समय असफल परीक्षण इकाइयों की अधिकता।",
+        "el": "Υπέρβαση αποτυχημένων μονάδων δοκιμής κατά την εκτέλεση εξειδικευμένων ελέγχων με μια δεδομένη συνάρτηση.",
+    },
 }
 
 

{pointblank-0.9.1 → pointblank-0.9.2}/pointblank/_interrogation.py

@@ -2248,6 +2248,107 @@ class ConjointlyValidation:
         return results_tbl
 
 
+class SpeciallyValidation:
+    def __init__(self, data_tbl, expression, threshold, tbl_type):
+        self.data_tbl = data_tbl
+        self.expression = expression
+        self.threshold = threshold
+
+        # Detect the table type
+        if tbl_type in (None, "local"):
+            # Detect the table type using _get_tbl_type()
+            self.tbl_type = _get_tbl_type(data=data_tbl)
+        else:
+            self.tbl_type = tbl_type
+
+    def get_test_results(self) -> any | list[bool]:
+        """Evaluate the expression get either a list of booleans or a results table."""
+
+        # Get the expression and inspect whether there is a `data` argument
+        expression = self.expression
+
+        import inspect
+
+        # During execution of `specially` validation
+        sig = inspect.signature(expression)
+        params = list(sig.parameters.keys())
+
+        # Execute the function based on its signature
+        if len(params) == 0:
+            # No parameters: call without arguments
+            result = expression()
+        elif len(params) == 1:
+            # One parameter: pass the data table
+            data_tbl = self.data_tbl
+            result = expression(data_tbl)
+        else:
+            # More than one parameter - this doesn't match either allowed signature
+            raise ValueError(
+                f"The function provided to 'specially()' should have either no parameters or a "
+                f"single 'data' parameter, but it has {len(params)} parameters: {params}"
+            )
+
+        # Determine if the object is a DataFrame by inspecting the string version of its type
+        if (
+            "pandas" in str(type(result))
+            or "polars" in str(type(result))
+            or "ibis" in str(type(result))
+        ):
+            # Get the type of the table
+            tbl_type = _get_tbl_type(data=result)
+
+            if "pandas" in tbl_type:
+                # If it's a Pandas DataFrame, check if the last column is a boolean column
+                last_col = result.iloc[:, -1]
+
+                import pandas as pd
+
+                if last_col.dtype == bool or pd.api.types.is_bool_dtype(last_col):
+                    # If the last column is a boolean column, rename it as `pb_is_good_`
+                    result.rename(columns={result.columns[-1]: "pb_is_good_"}, inplace=True)
+            elif "polars" in tbl_type:
+                # If it's a Polars DataFrame, check if the last column is a boolean column
+                last_col_name = result.columns[-1]
+                last_col_dtype = result.schema[last_col_name]
+
+                import polars as pl
+
+                if last_col_dtype == pl.Boolean:
+                    # If the last column is a boolean column, rename it as `pb_is_good_`
+                    result = result.rename({last_col_name: "pb_is_good_"})
+            elif tbl_type in IBIS_BACKENDS:
+                # If it's an Ibis table, check if the last column is a boolean column
+                last_col_name = result.columns[-1]
+                result_schema = result.schema()
+                is_last_col_bool = str(result_schema[last_col_name]) == "boolean"
+
+                if is_last_col_bool:
+                    # If the last column is a boolean column, rename it as `pb_is_good_`
+                    result = result.rename(pb_is_good_=last_col_name)
+
+            else:  # pragma: no cover
+                raise NotImplementedError(f"Support for {tbl_type} is not yet implemented")
+
+        elif isinstance(result, bool):
+            # If it's a single boolean, return that as a list
+            return [result]
+
+        elif isinstance(result, list):
+            # If it's a list, check that it is a boolean list
+            if all(isinstance(x, bool) for x in result):
+                # If it's a list of booleans, return it as is
+                return result
+            else:
+                # If it's not a list of booleans, raise an error
+                raise TypeError("The result is not a list of booleans.")
+        else:  # pragma: no cover
+            # If it's not a DataFrame or a list, raise an error
+            raise TypeError("The result is not a DataFrame or a list of booleans.")
+
+        # Return the results table or list of booleans
+        return result
+
+
 @dataclass
 class NumberOfTestUnits:
     """

{pointblank-0.9.1 → pointblank-0.9.2}/pointblank/_utils.py

@@ -490,6 +490,7 @@ def _get_api_text() -> str:
         "Validate.row_count_match",
         "Validate.col_count_match",
         "Validate.conjointly",
+        "Validate.specially",
     ]
 
     column_selection_exported = [