Skip to content

Remove responsibility for managing readonly flag from abstract Store hierarchy? #3186

@TomNicholas

Description

@TomNicholas

Copying @paraseba's suggestion from pydata/xarray#10457:

Long term, I'd love to see the responsibility for managing the readonly flag removed from the abstract Store hierarchy. It feels this is a concern that is beyond what a Store should know about. It would help us keeping the Stores abstract and focused. Readonly-ness sounds like a session concern, independent of the details of how to write zarr objects to different media.

cc @maxrjones @d-v-b

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew features or improvements

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      pFad - Phonifier reborn

      Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

      Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy