@@ -55,10 +55,9 @@ cycle warning.
55
55
In the past few releases, we've slowly introduced more functionalities under this
56
56
umbrella. ` __sklearn_clone__ ` and ` __sklearn_is_fitted__ ` are two examples.
57
57
58
- In the latest release, at the time of writing this post, we focused on the testing
59
- infrasutructure and estimator tag system. Estimator tags used to be private, and we
60
- were not sure about their design. In the 1.6 release, new tags are introduced and
61
- using them looks like the following:
58
+ In the 1.6 release, we focused on the testing infrastructure and estimator tag system.
59
+ Estimator tags used to be private, and we were not sure about their design. In the 1.6
60
+ release, new tags are introduced and using them looks like the following:
62
61
63
62
``` python
64
63
from sklearn.base import BaseEstimator, ClassifierMixin
@@ -75,7 +74,7 @@ class MyEstimator(ClassifierMixin, BaseEstimator):
75
74
```
76
75
77
76
The new tags mostly follow the same structure as the old tags, but there are certain
78
- changes to them. The main change is that the old ` _xfail_checks ` is no more present
77
+ changes to them. The main change is that the old ` _xfail_checks ` is no longer present
79
78
in the new tags. That tag was used to tell the common testing tools about the tests
80
79
which are known to fail and are to be skipped. That information is now directly passed
81
80
to the test functionalities. The old way of skipping a test was the following:
@@ -123,13 +122,13 @@ def test_with_parametrize_with_checks(estimator, check):
123
122
```
124
123
125
124
While working on the testing infrastructure, we have also been working on improving our
126
- tests and that means in this release we had a particularly higher number of changes in
127
- their names and what they do. The changes should have made it easier for developers to
128
- fix issues with their estimators. Note that you can now pass ` legacy=False ` to both
125
+ tests and that means in this release we had a particularly high number of changes in
126
+ their names and what they do. The changes will make it easier for developers to fix
127
+ issues with their estimators. Note that you can now pass ` legacy=False ` to both
129
128
` check_estimator ` and ` parametrize_with_checks ` to include only strictly API related
130
129
tests.
131
130
132
- The above changes means developers need to updated their estimators and depending on
131
+ The above changes mean developers need to update their estimators and depending on
133
132
what they use, write scikit-learn version specific code to handle supporting multiple
134
133
scikit-learn versions. To make that process easier, we've worked on a package called
135
134
[ ` sklearn_compat ` ] ( https://github.com/sklearn-compat/sklearn-compat/ ) . You can either
0 commit comments