Skip to content

Document the mutability assumptions for the interop protocol #56

Open
@rgommers

Description

@rgommers

This was just asked about at https://twitter.com/__AlexMonahan__/status/1430522318854377475. I'd say we should have a similar argument as https://data-apis.org/array-api/latest/design_topics/copies_views_and_mutation.html. We cannot prevent mutations in the protocol itself, and existing libraries already may have APIs that do mutate in-place. So we should recommend against it (but of course power users that really understand what they are doing could go right ahead and mutate to their hearts' content - this is the same as for the buffer protocol, DLPack et al.).

There's an earlier discussion at #10 (which was unrelated to the protocol). The general sentiment was that in-place operations must be avoided for a full dataframe API.

Right now https://data-apis.org/dataframe-protocol/latest/ says nothing about mutability, this should be added.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions