ak.without_field ---------------- .. py:module: ak.without_field Defined in `awkward.operations.ak_without_field `__ on `line 18 `__. .. py:function:: ak.without_field(array, where, *, highlevel=True, behavior=None, attrs=None) :param array: Array-like data (anything :py:obj:`ak.to_layout` recognizes). :param where: If str, the name of the field to be removed. If a sequence, it is interpreted as a path where to remove the field in a nested record. :type where: str or non-empy sequence of str :param highlevel: If True, return an :py:obj:`ak.Array`; otherwise, return a low-level :py:obj:`ak.contents.Content` subclass. :type highlevel: bool :param behavior: Custom :py:obj:`ak.behavior` for the output array, if high-level. :type behavior: None or dict :param attrs: Custom attributes for the output array, if high-level. :type attrs: None or dict Returns an :py:obj:`ak.Array` or :py:obj:`ak.Record` (or low-level equivalent, if ``highlevel=False``) with an existing field removed. This function does not change the array in-place. See :py:obj:`ak.Array.__delitem__` and :py:obj:`ak.Record.__delitem__` for a variant that changes the high-level object in-place. (These methods internally use :py:obj:`ak.without_field`, so performance is not a factor in choosing one over the other.)