I would add to this lists:
- check_array;
- check_consistent_length;
- check_X_y.
Those are very useful.
Arnaud
On 15 Sep 2014, at 20:03, Olivier Grisel <olivier.gri...@ensta.org> wrote:
> 2014-09-15 6:40 GMT-07:00 Mathieu Blondel <math...@mblondel.org>:
>> lightning is using the following utils:
>>
>> - check_random_state
>> - safe_sparse_dot
>> - shuffle
>> - safe_mask
>> - sklearn.utils.testing.*
>>
>> The latter is not big deal but I like importing assertions from the same
>> place.
>>
>> On a second thought, importing all public utils in __init__.py might quickly
>> become messy.
>> I like Andy's propsal of having no imports at all in __init__.py.
>> I suggest we move everything in __init__.py to a suitable submodule.
>>
>> For the utils which we make private, I suggest we make a deprecation cycle
>> for safety.
>> A lot of utils will likely become private so we could use a decorator
>> @deprecated_util to automate the task.
>
> I am generally OK with those suggestions.
>
> --
> Olivier
>
> ------------------------------------------------------------------------------
> Want excitement?
> Manually upgrade your production database.
> When you want reliability, choose Perforce
> Perforce version control. Predictably reliable.
> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
> _______________________________________________
> Scikit-learn-general mailing list
> Scikit-learn-general@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/scikit-learn-general
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
Scikit-learn-general mailing list
Scikit-learn-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/scikit-learn-general