data-analysis

These examples take quite a long time to run, and they make our documentation CI fail quite frequently due to timeout. It'd be nice to speed the up a little bit.

To contributors: if you want to work on an example, first have a look at the example, and if you think you're comfortable working on it and have found a potential way to speed-up execution time while preserving the educational message

Due to the changes mentioned here miguelgrinberg/Flask-Migrate#384 the output of flask_migrate is not being logged during alembic migrations. Looks like the alembic.ini file needs to be updated to include logging config for flask_migrate.

These chang

Pandas version checks

• I have checked that the issue still exists on the latest versions of the docs on master here

Location of the documentation

https://pandas.pydata.org/docs/dev/reference/api/pandas.DataFrame.to_hdf.html?highlight=to_hdf#pandas.DataFrame.to_hdf

Documentation problem

• dropna
• index

are missing from the docst

Summary

Aesthetically trivial, yet I've spotted a discrepancy with font sizes in our tooltip (front-end + back-end screenshots below).
I believe sections #1 and #2 should have the same font size?

![image](https://user-images.githubusercontent.com/27242399/139825179-4d62e3

Is your feature request related to a problem? Please describe.
When working with a big piece of text, I sometimes scroll down and copy some text into another tab. When switching back to the first tab, both the input and the output pane is back on top. So I don't know where I was working just now.

Describe the solution you'd like
After tab switching, scroll position should be remembere

Description: If a new version of OpenRefine is available a message is displayed: "New Version Download OpenRefine v3.5.1 now."

Question: Is it possible to disable this message?

Rationale: We run OpenRefine in a controlled environment, in which any software needs to be packaged and signed. The user cannot update the software. Therefore it would be nice not to display that message.

• Base README.md
• Quizzes
• Introduction base README
  • Defining Data Science README
  • Defining Data Science assignment
  • Ethics README
  • Ethics assignment
  • Defining Data README
  • Defining Data assignment
  • Stats and Probability README
  • Stats and Probability assignment
• Working with Data base README
  • Rel

Collection of follow-ups to #5827. These can/should be broken out into individual PRs. Many are relatively straightforward and would make a good first PR.

General

• Documentation (none was added in original PR).
• Release notes.
• Example notebook.
• Double-check how sm.tsa.arima.ARIMA works with fix_params (it should fail except when the fit method is statespace

The source link in page geometric_mean_score is
https://github.com/scikit-learn-contrib/imbalanced-learn/blob/dfc44e2/imblearn/utils/_validation.py#L492

However, it should be
https://github.com/scikit-learn-contrib/imbalanced-learn/blob/f1abf75/i

See:
gonum/gonum#845 (comment)

Tell us about the problem you're trying to solve

When releasing a new version of Airbyte (example) one must manually create a release. Failure/forgetting to create a release and a tag can cause confusion and in some case errors downstream (Airbyte Cloud build looks for tagged versions to fetch some resources, so if we didn't create a tagged com

The official instructions say to use joblib for pickling PyOD models.

This fails for AutoEncoders, or any other TensorFlow-backed model as far as I can tell. The error is:

>>> dump(model, 'model.joblib')
...
TypeError: can't pickle _thread.RLock objects

Note that it's not sufficient to save the underlying Keras S

Hello,

I believe having type hints would really improve this project.
I offer that from now on type hints are selected as a necessary condition for the upcoming changes in PRs.
This way code base would slowly converge to a type hinted one.

Also this issue could be tagged as a good first issue for volunteer collaborators :)

cc: @abidlabs

Ref:
https://docs.python.org/3/library/typing

Based on @karthikeyann's work on this PR rapidsai/cudf#9767 I'm wondering if it makes sense to consider removing the defaults for the stream parameters in various detail functions. It is pretty surprising how often these are getting missed.

The most common case seems to be in factory functions and various ::create functions. Maybe just do it for those?