[scikit-learn] Vote on SLEP010: n_features_in_ attribute
trev.stephens at gmail.com
Wed Dec 4 04:41:36 EST 2019
Not a core contributor, but what's with the "_in" bit? Just go with a
public n_features which I think a bunch of estimators already have? Feels
On Wed, Dec 4, 2019 at 8:22 PM Andrew Howe <ahowe42 at gmail.com> wrote:
> Excellent idea.
> J. Andrew Howe, PhD
> LinkedIn Profile <http://www.linkedin.com/in/ahowe42>
> ResearchGate Profile <http://www.researchgate.net/profile/John_Howe12/>
> Open Researcher and Contributor ID (ORCID)
> Github Profile <http://github.com/ahowe42>
> Personal Website <http://www.andrewhowe.com>
> I live to learn, so I can learn to live. - me
> On Tue, Dec 3, 2019 at 10:14 PM Nicolas Hug <niourf at gmail.com> wrote:
>> As per our Governance <http://scikit-learn.org/stable/governance.html>
>> document, changes to API principles are to be established through an
>> Enhancement Proposal (SLEP) from which any core developer can call for a
>> vote on its acceptance.
>> *SLEP010: n_features_in attribute *is up for a vote. Please see
>> *This SLEP proposes the introduction of a public n_features_in_ attribute
>> for most estimators*
>> Core developers are invited to vote on this change until 4 January 2020
>> by replying to this email thread.
>> All members of the community are welcome to comment on the proposal on
>> this mailing list, or to propose minor changes through Issues and Pull
>> Requests at https://github.com/scikit-learn/enhancement_proposals/.
>> scikit-learn mailing list
>> scikit-learn at python.org
> scikit-learn mailing list
> scikit-learn at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the scikit-learn