:orphan:

|rss_image|  **scikit-learn - 1/1** :ref:`Blog <ap-main-0>` :ref:`machine_learning (5) <ap-cat-machine_learning-0>`

.. |rss_image| image:: feed-icon-16x16.png
    :target: ../_downloads/rss.xml
    :alt: RSS

----


.. index:: scikit-learn


.. _ap-cat-scikit-learn-0:

scikit-learn - 1/1
++++++++++++++++++

.. blogpostagg::
    :title: scikit-learn 0.23
    :date: 2021-01-03
    :keywords: scikit-learn,0.23,0.24
    :categories: scikit-learn
    :rawfile: 2021/2021-01-03_skl.rst

    The unit test are run against
    :epkg:`scikit-learn` 0.23, 0.24.
    Some unit tests are failing with version 0.23.
    They were disabled instead of looking into a cause
    which does not appear with the latest version.
    It affects all classes inheriting from :class:`SkBase
    <mlinsights.sklapi.sklearn_base.SkBase>` where a model
    using it is trained. The issue happens in :epkg:`joblib`.




.. blogpostagg::
    :title: scikit-learn internal API
    :date: 2020-09-02
    :keywords: API
    :categories: scikit-learn
    :rawfile: 2020/2020-09-02_api.rst

    The signature of method `impurity_improvement
    <https://github.com/scikit-learn/scikit-learn/blob/master/
    sklearn/tree/_criterion.pxd#L65>`_ will change for version
    0.24. That's usually easy to handle two versions of scikit-learn
    even overloaded in a class except that method is implemented
    in :epkg:`cython`. The method must be overloaded the same way
    with the same signature. The way it was handled is implemented
    in PR `88 <https://github.com/sdpython/mlinsights/pull/88>`_.
    

    ...





----

|rss_image|  **scikit-learn - 1/1** :ref:`2018-05 (1) <ap-month-2018-05-0>` :ref:`2019-02 (4) <ap-month-2019-02-0>` :ref:`2019-03 (1) <ap-month-2019-03-0>` :ref:`2020-09 (1) <ap-month-2020-09-0>` :ref:`2021-01 (1) <ap-month-2021-01-0>`