Re: [scikit-learn] Monthly meetings between core developers + "Hello World"

Hi everyone, Remainder that the next monthly meeting is on Monday! Please update your project notes *before Friday* so we don't have extra work on the WE :) https://github.com/scikit-learn/scikit-learn/projects/15

Re: [scikit-learn] Can Scikit-learn decision tree (CART) have both continuous and categorical features?

On 9/15/19 8:16 AM, Guillaume Lemaître wrote: On Sat, 14 Sep 2019 at 20:59, C W > wrote: Thanks, Guillaume. Column transformer looks pretty neat. I've also heard though, this pipeline can be tedious to set up? Specifying what you want for every feat

Re: [scikit-learn] Vote on SLEP009: keyword only arguments

The SLEP says: This proposal suggests making only/most commonly/used parameters positional. The/most commonly/used parameters are defined per method or function, to be defined as either of the following two ways: * The set defined and agreed upon by the core developers, which should cover

Re: [scikit-learn] Vote on SLEP009: keyword only arguments

Sorry, I was on vacation ;)  +1 from me. On 9/17/19 7:28 PM, Joel Nothman wrote: If we were to assume Andy's vote in the positive, him having been a major proponent of this change, we would say this was accepted by a unanimous vote of a majority of core developers. Having tentatively accepted

Re: [scikit-learn] Vote on SLEP009: keyword only arguments

On 9/17/19 3:42 AM, Joel Nothman wrote: I think you mean keyword-only, Alex On Tue., 17 Sep. 2019, 4:11 pm Alexandre Gramfort, mailto:alexandre.gramf...@inria.fr>> wrote: Yes I am +1 for positional arguments for the __init__ of the estimators. Alex Albert: my position when r

Re: [scikit-learn] Vote on SLEP009: keyword only arguments

I think Alex's and my concerns are legit. The SLEP is asking "are you OK with forcing some parameters to be kwords only? We still don't know which ones though". I understand why you don't want to bike shed now, but that's a surprisingly mild SLEP, hence the questions. The only response I can