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

Screenshot

Using Superset 1.0.1

Here for dates fields :

Here for some prices

Description

When analysing data in a table, one expects them to be ni

Right now, grid search variables are resolved before the random samples are generated.

If we could toggle the order of resolution, we could support this: https://discuss.ray.io/t/is-there-a-way-to-run-the-same-hyperparameter-configuration-multiple-times/1412/12

There are many places where we could make use of Pathlib.

Look for any places that uses with open(...) and ask yourself:

• is the argument a string ?
• would it make sens to make it a Path(),
• how far upstream in the code can I make it a Path.

Don't try to bite more than you can chew (or more than I can review), try to fix 1 place at a time.

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

Summary

When import streamlit and supervisely_lib together in a project there occurs a TypeError.

Steps to reproduce

Code snippet:

import streamlit as st
import supervisely_lib as sly

If applicable, please provide the steps we should take to reproduce the bug:

1. run the code with streamlit run ...
2. see error/traceback when you open the streamlit page

🐛 Bug

Please reproduce using the BoringModel

Currently, the progress bar doesn't make distinction between running in a real terminal or being piped to logs.

When Lightning run in logs, it produces a prog_bar line for each change.

<img width="1659" alt="Screenshot 2021-03-23 at 09 10 40" src="https://user-images.git

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)

I'm using mxnet to do some work, but there is nothing when I search the mxnet trial and example.