You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When writing code consuming ibis objects as part of its api, I often want to write functions that take in ibis tables/columns/scalars/values. From a UX perspective it would be nice to export a few common types in the top-level namespace so I can refer to these types in both annotations and docs as ibis.Table instead of ibis.expr.types.Table.
For my use case ibis.Table and ibis.Column alone would be sufficient. For completeness exporting ibis.Scalar, ibis.Value, and maybe ibis.Deferred may also be nice.
The text was updated successfully, but these errors were encountered:
Adds `Table`, `Column`, `Scalar`, `Value`, and `Deferred` to the
top-level `ibis` namespace. These are mostly useful for downstream users
consuming the ibis api (either type-annotating their code, or using
`isinstance` checks).
Fixes#8717.
When writing code consuming
ibisobjects as part of its api, I often want to write functions that take in ibis tables/columns/scalars/values. From a UX perspective it would be nice to export a few common types in the top-level namespace so I can refer to these types in both annotations and docs asibis.Tableinstead ofibis.expr.types.Table.For my use case
ibis.Tableandibis.Columnalone would be sufficient. For completeness exportingibis.Scalar,ibis.Value, and maybeibis.Deferredmay also be nice.The text was updated successfully, but these errors were encountered: