# refuse_rows

<table class=".origin_table">
    <tr>
        <td style="text-align: left; border-style: hidden">*function*  of [dascore.core._spool_inventory](`dascore.core._spool_inventory`)</td>
        <td style="text-align: right; border-style: hidden">[source](https://github.com/DASDAE/dascore/blob/dev/dascore/core/_spool_inventory.py#L314-L332)</td>
    </tr>
</table>

:::{.padded_bottom_10pt}

:::{.def_block}


<b>refuse_rows</b>(<br>
    &nbsp;&nbsp;&nbsp;&nbsp;source_rows: DataFrame
,<br>
    &nbsp;&nbsp;&nbsp;&nbsp;reasons
,<br>
    &nbsp;&nbsp;&nbsp;&nbsp;summary: str
,<br>
)-> 'None'


:::

:::
Raise naming the patches an inventory verb cannot handle, and why.

Every refusal these verbs make has the same shape — a few patches out
of an archive, each with its own particular; naming them is the whole
value, since the fix is nearly always to one file or one inventory
entry. `reasons` holds a particular per row and None where the row is
fine, so a caller judges rows without also formatting them.