remove column mentions for now

Author: MarcoGorelli

spec/API_specification/dataframe_api/column_object.py

@@ -802,11 +802,6 @@ def to_array(self) -> Any:
         may choose to return a numpy array (for numpy prior to 2.0), with the
         understanding that consuming libraries would then use the
         ``array-api-compat`` package to convert it to a Standard-compliant array.
-
-        Notes
-        -----
-        To be guaranteed to run across all implementations, :meth:`may_execute` should
-        be executed at some point before calling this method.
         """
         ...
 

spec/API_specification/dataframe_api/dataframe_object.py

@@ -67,7 +67,7 @@ def shape(self) -> tuple[int, int]:
 
         Notes
         -----
-        To be guaranteed to run across all implementations, :meth:`may_execute` should
+        To be guaranteed to run across all implementations, :meth:`maybe_execute` should
         be executed at some point before calling this method.
         """
         ...
@@ -934,7 +934,7 @@ def to_array(self, dtype: DType) -> Any:
         understanding that consuming libraries would then use the
         ``array-api-compat`` package to convert it to a Standard-compliant array.
 
-        To be guaranteed to run across all implementations, :meth:`may_execute` should
+        To be guaranteed to run across all implementations, :meth:`maybe_execute` should
         be executed at some point before calling this method.
         """
 

spec/design_topics/execution_model.md

@@ -47,7 +47,7 @@ The Dataframe API has a `DataFrame.maybe_evaluate` for addressing the above. We
 as follows:
 ```python
 df: DataFrame
-df = df.may_execute()
+df = df.maybe_execute()
 features = []
 for column_name in df.column_names:
     if df.col(column_name).std() > 0:
@@ -62,22 +62,21 @@ For example, a dataframe which can convert to a lazy array could decide to ignor
 `maybe_evaluate` when evaluting `DataFrame.to_array` but to respect it when evaluating
 `float(Column.std())`.
 
-Operations which require `DataFrame.may_execute` to have been called at some prior
+Operations which require `DataFrame.maybe_execute` to have been called at some prior
 point are:
 - `DataFrame.to_array`
 - `DataFrame.shape`
-- `Column.to_array`
 - calling `bool`, `int`, or `float` on a scalar 
 
-Note now `DataFrame.may_execute` is called only once, and as late as possible.
+Note now `DataFrame.maybe_execute` is called only once, and as late as possible.
 Conversely, the "wrong" way to execute the above would be:
 
 ```python
 df: DataFrame
 features = []
 for column_name in df.column_names:
     # Do NOT do this!
-    if df.may_execute().col(column_name).std() > 0:
+    if df.maybe_execute().col(column_name).std() > 0:
         features.append(column_name)
 return features
 ```