'interesting' isn't directly supported by the following claim (i.e.,
that joblib can be more efficient than pickle), and also describing
this as interesting isn't very useful to the user in my opinion.
Recommend to use of `filename.joblib` instead of `filename.pkl` for models persisted via the joblib library to reduce confusion when it comes to time load a model, as it will be more clear whether a file was saved using the `pickle` or `joblib` library.
* remove stuff to be removed 0.19
* more changes
* remove classes from 0.19 whatsnew
* remove _LearntSelectorMixin
* remove ProjectedGradientNMF, load_lwf_*
* minor fixes
* remove more copy from logistic regression path
* remove lda, qda from __init__.__all__
* remove pg solver in nmf from tests etc
* remove class_weight="auto" from tests
* doctest change for decision_function_shape="ovr"
* remove transfrom from tree test, minor fixes to tree tests
* some fixes in the tests
* undo changes in functions which still allow 1d input...
* also allow 1d in scale
* more test fixes...
* last test fixes in forest and tree
* svm default value change doctest failures
* pep8
* remove more class_weight="auto" stuff
* minor cosmetics in docstrings deprecated / removed behavior.
* say that store_covariance has been moved to __init__ in discriminant_analysis
* Update model_persistence.rst
Mention a reason not to unpickle untrusted data.
Be more precise about using pickled data from different versions.
* Explicit warning about cross version pickling
* docs: fix broken and redirect links
see #7000
* docs: fix links
see #7000
* docs: merge with master
* docs: fix fnrs and tinyclues logo links
* docs: fix link reference in text
* docs: fix typo
* docs: added back in metaoptimize-qa paragraph
* docs: update language for defunct site
* docs: update stackexchange section
* docs: remove defunct site, move quora to top
* docs: remove defunct link and rearrange links
Passing 1D arrays to check_array, without setting `ensure_2d` to false now
raises a deprecation warning before reshaping it. This will later throw an
error.
All Scaler classes also throw warnings when 1D arrays are passed.
All unit tests/doctests are modified to ensure that no 1D arrays are passed,
except in explicit 1D array tests where the warnings have been silenced.
Additional tests are also included which check for different 1D array cases.
2D array tests with one samples and one features are also added and where
they failed, `check_array` call has been modified to give a more useful error
message
Thomas Moreau