Skip to content

memory storage #144

Open
Open

Description

@d-v-b

In the context of using a zarrs-backed codec pipeline on in-memory storage:

Don't think so since this package doesn't support that kind of store crossing into rust

Originally posted by @ilan-gold in #143 (comment)

what would we need to change in zarr-python to enable this?

Activity

  1. LDeakin commented on Feb 2, 2026

    @LDeakin
    Member

    Likely nothing on your end. I'd guess if obstore is implemented properly (#139), it could just be done via an obstore in memory store.

  2. ilan-gold commented on Feb 2, 2026

    @ilan-gold
    Collaborator

    Likely nothing on your end. I'd guess if obstore is implemented properly (#139), it could just be done via an obstore in memory store.

    Was just typing, the cleanest way would be to expose a store in python that has its "memory" in rust but is accessible via python (I can think of a lot of other terrible ways to do this)

  3. d-v-b commented on Feb 2, 2026

    @d-v-b
    Author

    great to hear! over in zarr-developers/zarr-python#3679 I put in a framework for handling "memory://.." URLs. That's pure python, but the eventual idea is that a store (like obstore) could register a handler for the "memory://" scheme.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions