Skip to content

Inconsistent tocoo/to_coo methods on different sparse types #507

@mangecoeur

Description

@mangecoeur
Contributor

There is some inconsistencies in the naming of to-coo methods: GCXS has tocoo, DOK has to_coo. I assume to some extent it's to have some compatibility with scipy sparse. But then why not just have both methods on all types?

Activity

added
bugIndicates an unexpected problem or unintended behavior
on Aug 11, 2021
hameerabbasi

hameerabbasi commented on Aug 20, 2021

@hameerabbasi
Collaborator

We're considering deprecating those and using asformat always instead.

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

    bugIndicates an unexpected problem or unintended behavior

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @mangecoeur@hameerabbasi

        Issue actions

          Inconsistent tocoo/to_coo methods on different sparse types · Issue #507 · pydata/sparse