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

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

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

Travis is not going to automatically offer the free tier for all open source projects; We likely want o migrate away from travis.

Setting up github actions to replace travis would be a welcomed contribution.

Describe your feature request

Throughout our codebase, we don't use warnings.warn and rather rely on logger.warn to inform users of possible negative outcomes.

Instead, we should use warnings.warn appropriately:

https://docs.python.org/2/howto/logging.html#when-to-use-logging

In recent versions (can't say from exactly when), there seems to be an off-by-one error in dcc.DatePickerRange. I set max_date_allowed = datetime.today().date(), but in the calendar, yesterday is the maximum date allowed. I see it in my apps, and it is also present in the first example on the DatePickerRange documentation page.

E

Not a high-priority at all, but it'd be more sensible for such a tutorial/testing utility corpus to be implemented elsewhere - maybe under /test/ or some other data- or doc- related module – rather than in gensim.models.word2vec.

Originally posted by @gojomo in RaRe-Technologies/gensim#2939 (comment)

🚀 Refactoring

As isort has been added to ci in #4242, we now need to apply the formatter step by step i.e. a submodule per PR (recommended in PyTorchLightning/pytorch-lightning#4242 (comment) by @Borda)

Steps

For each PR:

1. choose one submodule from below list and apply isort to it
2. remove the corresponding line in pyproject.toml
3. make

more details at: allenai/allennlp#2264 (comment)

What would you like to be added: As title

Why is this needed: All pruning schedule except AGPPruner only support level, L1, L2. While there are FPGM, APoZ, MeanActivation and Taylor, it would be much better if we can choose any pruner with any pruning schedule.

**Without this feature, how does current nni

We have too much padding on menu entries in the left-hand side bar of the docs:

This was probably introduced by mistake in #3178.

We should restore this padding to Docusaurus' defaults - the area that needed more padding is on the right-hand side (see PR discussion).

Mentioned b