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.

See:

https://github.com/pytorch/pytorch/blob/7b939d934ee900e5d7c1df858a3f4e413b434592/test/test_ops.py#L161

Currently this test requires setting supports_inplace_autograd, but that setting seems silly when the operation doesn't have an inplace variant. We should just skip this test for ops without an inplace variant.

cc @mruberry @VitalyFedyunin @walterddr

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

The list is rather long, and getting longer with time, so I think it would be best to keep it sorted alphabetically, to make lookup easier.

Currently the tabs on SQL Lab queries show green circle when a query is running as well as when a query has successfully finished.

The green circles for "query running" and "query completed" could be made more distinct - different color, or having the "query running" circle be hollow, and the "query completed" one filled in. This would enable users, who might go to SQL Lab and trigger few quer

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

Currently Styler.clear() will clear the styles built up with the apply aaplymap and where method. It will clear class from the set_td_classes method and it will clear tooltips set with set_tooltips.

It does not clear table styles, and it does not clear formats. It does not reset hidden index or hidden columns.

Thoughts and PR into what this should do and how it should it be docum

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