Skip to content
This repository was archived by the owner on Feb 14, 2018. It is now read-only.
This repository was archived by the owner on Feb 14, 2018. It is now read-only.

Improve block naming interface #3

@ixjlyons

Description

@ixjlyons

Mandating that every block class take a name kwarg is a pain, but assuming the name is the class name could lead to conflicts if a block type is reused (definitely a possibility with e.g. Filter). It only really matters in the context of a pipeline, but mandatory naming when constructing a pipeline is also a bit painful. The scikit-learn solution wouldn't work well because of how pipeline structure is specified in copper.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions