@@ -17,7 +17,7 @@ This proposal discusses the path to gradually forcing users to pass arguments,
17
17
or most of them, as keyword arguments only. It talks about the status-quo, and
18
18
the motivation to introduce the change. It shall cover the pros and cons of the
19
19
change. The original issue starting the discussion is located
20
- `here <https://github.com/scikit-learn/scikit-learn/issues/12805 >`_ .
20
+ `here <https://github.com/scikit-learn/scikit-learn/issues/12805 >`__ .
21
21
22
22
Motivation
23
23
##########
@@ -110,8 +110,8 @@ following two definitions may also be confusing to some users:
110
110
However, some other teams are already moving towards using the syntax, such as
111
111
``matplotlib `` which has introduced the syntax with a deprecation cycle using a
112
112
decorator for this purpose in version 3.1. The related PRs can be found `here
113
- <https://github.com/matplotlib/matplotlib/pull/13601> `_ and `here
114
- <https://github.com/matplotlib/matplotlib/pull/14130> `_ . Soon users will be
113
+ <https://github.com/matplotlib/matplotlib/pull/13601> `__ and `here
114
+ <https://github.com/matplotlib/matplotlib/pull/14130> `__ . Soon users will be
115
115
familiar with the syntax.
116
116
117
117
IDE Support
@@ -151,7 +151,7 @@ An important open question is which functions/methods and/or parameters should
151
151
follow this pattern, and which parameters should be keyword only. We can
152
152
identify the following categories of functions/ methods:
153
153
154
- - `` __init__ `` s
154
+ - `` __init__ ``
155
155
- Main methods of the API , * i.e.* `` fit`` , `` transform`` , etc.
156
156
- All other methods, * e.g.* `` SpectralBiclustering.get_submatrix``
157
157
- Functions
@@ -168,8 +168,8 @@ defined as either of the following two ways:
168
168
the * easy* cases.
169
169
- A set identified as being in the top 95 % of the use cases, using some
170
170
automated analysis such as `this one
171
- < https:// odyssey.readthedocs.io/ en/ latest/ tutorial.html> `_ or ` this one
172
- < https:// github.com/ Quansight- Labs/ python- api- inspect> `_ .
171
+ < https:// odyssey.readthedocs.io/ en/ latest/ tutorial.html> `__ or ` this one
172
+ < https:// github.com/ Quansight- Labs/ python- api- inspect> `__ .
173
173
174
174
This way we would minimize the number of warnings the users would receive,
175
175
which minimizes the friction cause by the change. This SLEP does not define
0 commit comments