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

System information

• TensorFlow version: 1.13.1
• Doc Link: https://www.tensorflow.org/api_docs/python/tf/cus

As discussed in #3926, the following files do not have .py extensions because TensorFlow does not yet support the current Python.

• dynamic_programming/k_means_clustering_tensorflow.py_tf
• machine_learning/lstm/lstm_prediction.py_tf
• neural_network/gan.py_tf
• neural_network/input_data.py_tf

TODO: Restore the .py file extensions

(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.

🐛 Bug

I stumbled upon excessive CPU usage for my training code running on GPU. After some investigations I found the culprit.
It basically was

x = torch.eye(256).to('cuda') 

To Reproduce

This is quick and loads single CPU core.

%%timeit
    torch.eye(181)
6.43 µs ± 218 ns per loop (mean ± std. dev. of 7 runs, 100000 loops each)

This is 3 times slowe

It appears that the docs for Logistic Regression differ based on solvers and penalties. The "penalty" parameter states that "The ‘newton-cg’, ‘sag’ and ‘lbfgs’ solvers support only l2 penalties," while the "solver" parameter states that "‘newton-cg’, ‘lbfgs’, ‘sag’ and ‘saga’ handle L2 or no penalty" (attaching some screenshots). This was actually a little unclear to me, as I wasn't sure if the n

@apalala reported this issue when a site sends some invalid images, and suggested a fix for the spider middleware:

        image_stream = self.get_images(response, request, info, item=item)
        while True:
            try:
                path, image, buf = next(image_stream)
            except StopIteration:
                break
            except Exception:
                co

If a metric is removed from a datasource the single metric widget is inoperable if saved slice or URL references the previously defined metric. Note this isn't a problem for visualization types which support multiple metrics.

Expected results

The metric widget to render correctly.

Actual results

The metric widget in inoperable (see attached screenshot).

Screenshots

<

Hello everyone, I will explain the current status of manim in this issue.

Now there are three main manim versions, and their differences:

1. The master branch of 3b1b/manim: Rendering on GPU using OpenGL and moderngl. Support interaction and have higher efficiency.
2. ManimCommunity/manim: (@ManimCommunity

First check

• I added a very descriptive title to this issue.
• I used the GitHub search to find a similar issue and didn't find it.
• I searched the FastAPI documentation, with the integrated search.
• I already searched in Google "How to X in FastAPI" and didn't find any information.
• I already read and followed all the tutorial in the docs and didn't find an answ

This check is no longer relevant:

https://github.com/pandas-dev/pandas/blob/9ab55b4aed9018b070c939ffbdf232f99bf50f1a/.pre-commit-config.yaml#L83-L88

Since using PEP604 rewrites, this would be written as

x: Series | DataFrame

anyway.

x: FrameOrSeriesUnion

is actually just as long as the above, and arguably less explicit.

@simonjayhawkins thoughts on replacin