Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Public vs. private utils again #6616

Closed
Closed
@mblondel

Description

@mblondel

Now that we created scikit-learn-contrib, one of scikit-learn's roles is to ease the creation of new contrib projects. So we really need to sort out the public vs. private utils issue once and for all. Despite many discussions, AFAIK, we haven't reached a consensus or come up with a realistic plan.

Whether we like it or not, people do use utils and they complain when utils break.

Based on this I propose that

  1. All current utils are now officially public and if we change them, we need to apply the usual 2 release compatibility rule.
  2. From now on, new utils should be made private (i.e., start with a leading underscore) unless we have a good reason to make them public. In other words, we should think twice before making an util public.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions