@@ -541,7 +541,7 @@ Let's dive in!
541
541
542
542
16. Compile, then run the relevant portions of the regression-test suite.
543
543
This change should not introduce any new compile-time warnings or errors,
544
- and there should be no externally- visible change to Python's behavior.
544
+ and there should be no externally visible change to Python's behavior.
545
545
546
546
Well, except for one difference: ``inspect.signature() `` run on your function
547
547
should now provide a valid signature!
@@ -1117,7 +1117,7 @@ Here's the syntax for cloning a function::
1117
1117
``module.class `` in the sample just to illustrate that you must
1118
1118
use the full path to *both * functions.)
1119
1119
1120
- Sorry, there's no syntax for partially- cloning a function, or cloning a function
1120
+ Sorry, there's no syntax for partially cloning a function, or cloning a function
1121
1121
then modifying it. Cloning is an all-or nothing proposition.
1122
1122
1123
1123
Also, the function you are cloning from must have been previously defined
@@ -1315,7 +1315,7 @@ to specify in your subclass. Here's the current list:
1315
1315
there is no default, but not specifying a default may
1316
1316
result in an "uninitialized variable" warning. This can
1317
1317
easily happen when using option groups—although
1318
- properly- written code will never actually use this value,
1318
+ properly written code will never actually use this value,
1319
1319
the variable does get passed in to the impl, and the
1320
1320
C compiler will complain about the "use" of the
1321
1321
uninitialized value. This value should always be a
0 commit comments