On Thu, Jul 28, 2016 at 5:10 PM, Andreas Mueller <[email protected]> wrote: > > > On 07/28/2016 12:03 PM, Matthew Brett wrote: >> >> Hi, >> >> On Wed, Jul 27, 2016 at 10:08 PM, Andreas Mueller <[email protected]> >> wrote: >>> >>> Hi Daniel. >>> This hasn't been brought up before so there is no "official position". >>> I am generally in favor, though I'm not sure how doable it is. >>> We are generally pretty generous in accepting all kinds of inputs, and >>> many >>> of our options can have different types: (None, int, float, string, >>> nd-array) is relatively common as a type for an option. >>> As we still support 2.6, we would need to do comments or external files. >> >> Given numpy has dropped support for 2.6, maybe it would be reasonable >> for scikit-learn to do the same, to make this process easier? >> > How would it change the process? > We have been discussing this. My stance is that we should drop it > as soon as it creates a major nuisance, but not just for the sake > of dropping it.
Ah - sorry - I misunderstood this: > As we still support 2.6, we would need to do comments or external files. to mean 2.6 specifically, rather than 2.x. Cheers, Matthew _______________________________________________ scikit-learn mailing list [email protected] https://mail.python.org/mailman/listinfo/scikit-learn
