Please make sure that this is a bug. As per our
GitHub Policy,
we only address code/doc bugs, performance issues, feature requests and
build/installation issues on GitHub. tag:bug_template

System information

• Have I written custom code (as opposed to using a stock
  example script provided in TensorFlow): Yes

currently, some of the programs use static type checking like this program but some of the programs did not use static typing.

it's a good practice to use static typing as it makes code more clear and readable, should we make it a standard for this repository.we can use mypy for

(e.g. for links and images), because some of these examples are now being rendered in the docs.

Added by @fchollet in requests for contributions.

Describe the issue linked to the documentation

Follows from #17387

Suggest a potential alternative/fix

Stop referencing preprocessing functions e.g. :

maxabs_scale
minmax_scale
normalize
quantile_transform
robust_scale
scale
power_transform

in the UG, and only add them e.g. in the "See Also" sections, or even just in the API ref.

In particular right now the first entr

WARNING: /data/users/ezyang/pytorch-tmp/BUILD.bazel:580:1: in hdrs attribute of cc_library rule //:aten_headers: Artifact 
'bazel-out/k8-fastbuild/bin/aten/src/ATen/Config.h' is duplicated (through '//:aten/src/ATen/Config.h' and '//:aten_src_AT
en_config'). Since this rule was created by the macro 'cc_library', the error might have been caused by the macro implemen
tation                 

It looks like Travis support specifying such a Python version as 3.9-dev.

While I’m not sure we should officially support Python 3.9 it until its release, running tests on it will allow us to catch any issue early.

At some point we moved from using mocha as a test runner to using jest, and jest out of the box started reporting much more warnings than mocha did.

No one went to clean up this output. In many cases it may just be about passing an extra prop in a component or setting a proper default value for a component's prop, or adding up to an existing fixture.

[optional] please roll out in chu

Copied from #7991:

If you look at https://certbot.eff.org/docs/api/certbot.compat.filesystem.html, you'll notice many formatting errors which should be fixed.

That's the bare minimum which I think should be done, but I think we should also see what we can do to avoid these problems from happening in the future. Is there a way we could build the docs in CI and check for these problems?

The new version of black is consistent in how it handles the magic trailing commas. So if we upgrade black and apply it, lots of files will be changed. However, the diff needn't be so large if we remove unnecessary trailing commas before upgrading.

E.g. in pandas/core/aggregation.py there is

def reconstruct_func(
    func: Optional[AggFuncType], **kwargs,
) -> Tuple[
    bo