Niels Bantilan

hey @bfmcneill the current behavior is that `DataFrameSchema(coerce=True)` will override the coerce setting at the column/index level. This is not currently explicitly documented anywhere. It would probably belong [here](https://pandera.readthedocs.io/en/stable/dataframe_schemas.html#coercing-types-on-columns) right...

thanks @Zac-HD! > This is OK (ish, usually) for scalars, but adds up really fast when you're rejecting whole columns or dataframes. So "try to filter elements, not columns" is...

thanks @Zac-HD! will update the minimum `hypothesis` version and make these improvements. > The downside is of course no keyword arguments or type annotations Thats okay, currently we're using lambda...

hi @jgirault-qs thanks for pointing this out! there are two things here to improve the experience: 1. add documentation to document the behavior of `n_failure_cases` 2. set the default for...

cool, thanks @Patil2099! Head over the the [contributing guide](https://pandera.readthedocs.io/en/stable/CONTRIBUTING.html) to see how to set up your dev environment

Hey @Patil2099 just checking in: are you still able to tackle this issue?

### UnionML OSS Planning Notes: This functionality is relevant for integrations with: - whylogs - revela ```python from unionml.callbacks import RevelaMonitoringCallback @model.predictor(post_callback=RevelaMonitoringCallback()) def predictor(model: ModelType, features: FeatureType) -> PredictionType: predictions...

fixed by https://github.com/conda-forge/staged-recipes/pull/19349

Re-opening this... just need to add conda-forge install instructions in the README and [installation](https://unionml.readthedocs.io/en/latest/#installation) section of the docs, then we can close this

This task has already been assigned... @ManishS6 do you still have capacity to work on this issue?