Niels Bantilan

> Enjoying the Pandera package a lot! And thank you 😀

this use case makes sense... I agree pyarrow should be an optional dependency (not a package extra). Removing this as a dependency from the project, we need to: - remove...

@markkvdb are you open to making a PR for this change?

Hey, @benlindsay this proposal looks good to me! One minor naming/API change I'd suggest is perhaps to do `Field(on_missing="warn")` and `on_missing_columns="warn"` for the schema model config. I think this is...

cool! just added the "help wanted" tag on this issue. In the mean time, here's a perhaps useful extension to the code snippet you provided: ```python class UserSchema(pa.SchemaModel): id: Series[int]...

hi @g-simmons, this looks like a performance issue on the dataframe strategy generation function. I suspect it has something to do with this: https://github.com/pandera-dev/pandera/blob/master/pandera/strategies.py#L1104-L1112 ```python for col_name, col_dtype in col_dtypes.items():...

Hi @MikiGrit thanks for articulating the feature request! gonna ping @aodj here too, who created a very similar issue (#893). In short: yes! I give my blessing to support this...

hi @zevisert thanks for proposing this, it's a great idea! I think the syntax of idea # 1 will be more useful and expressive, since you can also provide `pa.Field`...

I'm down for introducing a new `Model` base class that handles this case, although I'd like to propose a slightly different naming to be `ArrayModel`. ```python class DatetimeAmount(pa.ArrayModel): name: P.Int32...

> I suggest an argument pa.Field(index:bool) that would only apply to "arrays" supporting an index. Cool! This sounds good to me... it's also nice because it doesn't shoe-horn `ArrayModel` to...