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.

It should be added to the .rst so that they appear on the website.
Doc is already inline here https://github.com/pytorch/pytorch/blob/df88cc3f7f5c13221a93d7d3d38e681a3d5a6b6a/torch/nn/modules/module.py#L89-L115

cc @jlin27 @mruberry

Most functions in scipy.linalg functions (e.g. svd, qr, eig, eigh, pinv, pinv2 ...) have a default kwarg check_finite=True that we typically leave to the default value in scikit-learn.

As we already validate the input data for most estimators in scikit-learn, this check is redundant and can cause significant overhead, especially at predict / transform time. We should probably a

Im using code from Scrapy documentation - https://docs.scrapy.org/en/latest/topics/exporters.html, with "Product" class item created

from scrapy.exporter import XmlItemExporter

class ProductXmlExporter(XmlItemExporter):

    def serialize_field(self, field, name, value):
        if field == 'price':
            return f'$ {str(value)}'
        return super(Product, self).serialize_fi

Screenshot

N/A

Description

Right now whenever users search for queries they are case sensitive. We should remove this to allow users to put in term with any cases

Design input

[describe any input/collaboration you'd like from designers, and
tag accordingly. For design review, add the
label design:review. If this includes a design proposal,
include the label `design:suggest

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: (probably the most used currently) rendering on the CPU using cairo, currently stable.
2. The shaders branch of 3b1b/manim: (Grant is making, usi

We have a couple of dataframe tests (xref #13304) related to column ordering when constructed from an OrderedDict:
https://github.com/pandas-dev/pandas/blob/e4cf3abe0020aa801950e0383fffc13ee9703456/pandas/tests/frame/test_constructors.py#L1250-L1288

As of PEP 468 standard dictionaries are ordered so these tests should also work with OrderedDict

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?